Skip to main content
POST /orders issues tickets the way the Tickable dashboard does for guests and reservations. It needs the orders.write scope.

​
Free tickets

A guest list, a prize, a partner: the tickets are issued at once and mailed to the buyer.
Pass "send_mail": false to issue them without a mail; the response’s order_url is the buyer’s page with the tickets. With "payment": "link" the order keeps its places until expires_at (default 24 hours, at most 30 days) and waits for payment. The buyer gets a mail with the link, and the response carries the same link as payment_url: send people there from your own site, Tickable’s hosted page handles iDEAL, Bancontact and card. The service fee is added there, just like in the shop. Not paid in time, the order is removed and its places go back on sale.
Once it is paid you receive the order.confirmed webhook, as for every order.

​
Good to know

  • timeslot_id may be left out when the event has exactly one timeslot.
  • Capacity and the timeslot’s ticket types are checked in one transaction, so two requests cannot take the last place. A full timeslot returns 409 with code sold_out.
  • Sale windows do not apply, the same as for tickets issued from the dashboard. Check availability first if your site should follow them.
  • Always send an Idempotency-Key: a retry after a timeout then returns the same order instead of issuing a second one.
  • The user who created the API key needs the right to issue tickets in the organization.