Skip to content

Build on Speakeasy

Venues use Speakeasy to sell tickets and tables, know their guests and run the door. These pages show how to connect your own website, app or data systems to it.

What you can build

  • Show events and tables on your own site or app, with live prices and availability.
  • Send guests straight to booking with links that open the right event, table and party size.
  • Put our checkout on your website, so the guest does not leave your page.
  • Keep your CRM or data warehouse up to date with guests, orders, table reservations, refunds and disputes.
  • Send us guest lists from your own tools.
  • Pass conversations to the venue team from your own chat or text service.
  • Hear about new orders, refunds, check-ins and opt-outs as they happen, with webhooks.
  • Update your site when an event changes, with a webhook.

Which way to integrate

You want to Use Who takes the payment Start here
Show events and tables The API - Show events and tables
Send guests to book from your site or app Links from the API Speakeasy Links to booking
Keep guests on your website during checkout The checkout widget Speakeasy Put our forms and checkout on your site
Collect guest list sign-ups or table requests on your site The embedded forms - Put our forms and checkout on your site
Copy guests, orders and reservations into your own systems The API - Sync orders, reservations and guests
Hear about new orders, refunds, check-ins and opt-outs as they happen Webhooks - Webhooks
Send us guest lists or Concierge entries The API - Guest lists, Concierge

Selling inside your own app

Selling tickets or tables through the API with your own checkout is not available today. If you need it, talk to your Speakeasy contact.

Two kinds of key

We have two groups of routes today, and each has its own kind of key.

API key Venue key
Routes /external/v1/... /partners/...
Covers Many venues, chosen for your integration One venue
Good for New integrations: events, ticket types and tables, syncing guests, orders and reservations, webhooks, guest lists and Concierge entries Integrations that already use it
Answers Mapped fields, with paging Full records, mostly without paging
Reference API reference Venue routes

Both keys go in the same header, token. Your Speakeasy contact gives you the key you need. New integrations should use the API key wherever the API has what they need.

Next