API Frequently Asked Questions

This section contains the answers to common questions related to Onebox's APIs.

If you cannot find an answer to your question, contact us or open a ticket at the API Support Help Center.

Common questions

Who manages payment processing — the API or my integration?

Payment processing happens outside the Onebox APIs. Your integration is responsible for the payment provider integration (Stripe, PayPal, Redsys, etc.). Onebox only marks the order as paid once your integration calls POST /orders/confirm after a successful payment. See the Purchase flow for the full sequence.

How are taxes handled in order totals?

All prices returned by the APIs are tax-inclusive. Some responses include a tax breakdown for informational purposes, but your integration does not need to compute taxes on top of the listed prices.

Can I send custom fields in the buyer or attendee data?

Yes. If you need an additional field that is not part of the standard schema, request it from our operations team once your integration is in the production environment. The field will be enabled per channel.

How do I know if a session requires attendee (nominal) data?

Check attendee_settings in the session availability response, or items[].attendee.required after adding items to the order. See Understanding Attendee Requirements for details.