Developer docs

Quickstarts

Your first booking in five minutes, one page per integration path — JavaScript, WordPress, .NET, plain REST and an AI assistant over MCP.

Every path below ends the same way: a real reservation at the demo venue demo-sportsbar, or at your own venue once you swap the slug and the key. Pick the one that matches where your code runs.

You have Start here You end up with Time
A web page, and you want a booking form on it JavaScript The widget on your page, plus the headless client for your own form 5 minutes
A WordPress site WordPress A page with the booking shortcode 5 minutes
A .NET application or service .NET The typed client registered and one booking made from code 5 minutes
Any other language or a terminal REST API Three calls: read the venue, find a free slot, book it 5 minutes
Claude, ChatGPT or VS Code MCP server Your assistant connected, finding a venue and booking a table 5 minutes

What every path needs

  • An API key. A publishable key (bdp_pk_…) for code that runs in a browser, a secret key (bdp_sk_…) for code that runs on a server. Create either in the console under Venue → API keys; Authentication explains the difference and why the two are never swapped. The MCP path needs no key: you sign in with your account.
  • A venue slug. Your venue's slug is shown in the console's venue settings. The snippets use demo-sportsbar, BookDinePlay's fictional demo venue, so you can read them against real data before you have a venue of your own.

The snippets are tested

Every code block on these pages is checked when BookDinePlay is built, so a quickstart cannot drift away from the product. The .NET snippet is compiled and run against the API on every change, the JavaScript snippet is run against a stub of the SDK's network layer, and every cURL command is matched against the API's OpenAPI description: the method, the route, the headers, the query parameters and the body fields must all exist. If you find a snippet that does not work, tell us.

After the quickstart

  • Tutorials take one feature all the way through: deposits, events with tickets, gift vouchers, several venues, QR ordering and AI-agent workflows.
  • API reference documents every route, field and refusal.
  • Versioning and compatibility says what we promise to keep working, and the Changelog lists what changed.