Creating orders

POST /v1/orders creates a completed order with tickets for one ticket type, for example from your own registration system. The money is collected outside Tixxy.

Fees and requirementsCopy Anchor Link

Tickets created through the API are regular tickets that can be downloaded, scanned and personalised, so the regular Tixxy fee applies to every ticket. For a live token with orders:write:

• the fee terms were accepted when the token was created;
• the organisation needs an active direct debit mandate. When it is revoked, requests fail with 403 billing_mandate_required.

Test tokens have neither requirement and create free test orders.

RequestCopy Anchor Link

{
  "ticket_type": "tt_01J...",
  "quantity": 2,
  "booker": {
    "first_name": "Jane",
    "last_name": "Doe",
    "email": "jane@example.com",
    "language": "nl"
  },
  "answers": { "phone": "+31612345678" },
  "tickets": [
    { "answers": { "first_name": "Jane", "last_name": "Doe" } },
    { "answers": { "first_name": "John", "last_name": "Doe" } }
  ],
  "external_reference": "CRM-5012",
  "send_confirmation": true
}

• answers holds the booker's answers to the event's form fields, keyed by field key.
• tickets[].answers holds answers per ticket, in order. Leave a ticket out to let the holder fill it in later through personalisation.
• event_days is required for ticket types where the buyer picks days: a list of day_ ids.
• send_confirmation (default true) emails the booker.

The API checks stock and day capacity and enforces the maximum per order. Answers are validated with the event's own form field rules.

Always send an Idempotency-Key.