Barq Meet
Create your free link

Booking API and webhooks for your own application

On this page

What could I build with the booking API?

You could put a date picker inside your own client portal, submit the chosen slot through the API, then update your customer record from a booking webhook. We apply the same booking checks as the hosted flow. You supply the interface and handle errors. Start with one request.

If you only need our booking form inside your website, choose an embed instead. The developer reference and OpenAPI document describe the actual contract.

# Set APP_ORIGIN to your app origin and BOOKING_SECRET_KEY on your server.
curl "$APP_ORIGIN/api/v1/event-types"   -H "Authorization: Bearer $BOOKING_SECRET_KEY"

This server-side read lists active public events. It doesn't create a booking. We require a secret key for host-wide booking access and for including secret events in the event list.

Connect the booking action to your own records

Create keys and webhook subscriptions in Settings, "API & webhooks". Read available slots before creating a booking, then handle webhook notifications as changes to an existing record. We include a payload ID so repeated deliveries can be recognized, which lets your application distinguish a delivery retry from another change to a booking. Keep processing safe to repeat.

Read availability, create the booking, then process signed changes
  1. 1

    Read events and slots

    Authenticate with a key; select a valid event and available start time.

  2. 2

    Create the booking

    Submit the guest fields and use Idempotency-Key for retries.

  3. 3

    Receive a webhook

    Validate the timestamp and signature against the original request body.

  4. 4

    Update your records

    Deduplicate by payload ID and record the booking state in your application.

Read availability, create the booking, then process signed changes
StepTitleDetails
1Read events and slotsAuthenticate with a key; select a valid event and available start time.
2Create the bookingSubmit the guest fields and use Idempotency-Key for retries.
3Receive a webhookValidate the timestamp and signature against the original request body.
4Update your recordsDeduplicate by payload ID and record the booking state in your application.

Source: REST booking routes and webhook delivery behavior, checked 17 Nov 2026. Create a webhook subscription for the booking events you need, then send a test delivery and inspect its response code.

Which API credentials belong in a browser?

Only publishable keys belong in browser code, with the page's exact origin on the key's allowed list. Secret keys are for server requests and are rejected when a browser Origin header is present. We enforce that distinction at authentication. Never paste a secret into frontend code.

Browser booking creation also requires the documented anti-abuse token. Canceling, rescheduling or reading a guest booking with a publishable key needs its management token; a server-side secret key grants the host's access.

Default limits separate several scopes: 600 requests per minute and 20,000 per day per key, plus 60 writes per minute per key. Booking creation also has an IP allowance of 10 per minute and 60 per hour. These are configurable defaults; honor Retry-After when a request is limited.

Start with the custom booking-page walkthrough to connect slot selection, submission and retry handling in one guest flow.

How should I check a signed booking webhook?

Verify the BarqMeet-Signature header using your webhook signing secret and the original body bytes. Its format is t=<timestamp>,v1=<hex digest>, where the digest is HMAC-SHA256 of <timestamp>.<raw body>. Check timestamp freshness before accepting the message, and compare the received signature with the expected digest using a constant-time comparison to avoid timing leaks. Re-serialising parsed JSON changes those bytes.

We send booking lifecycle notifications, including requests and approval decisions, and retain delivery response codes for troubleshooting. Store the notification before responding successfully so a temporary failure doesn't lose the update.

Insights explains booking attribution carried in booking data. API access has no paid tier; pricing covers fair use. Create an account for your integration.

Frequently asked questions

Can a publishable key cancel or reschedule a booking?

Yes, with that booking's management token. A publishable key alone doesn't grant host access to bookings. Use the token for guest actions, or a server-side secret key when your application needs to act as the host. Keep host-wide management operations on the server and inspect the endpoint's authentication requirements before exposing a control in the browser.

Can I safely retry a booking request after a timeout?

Yes. Send an Idempotency-Key header when creating a booking and reuse that same value for the retry. The API supports idempotent creation so your integration can recover from a lost response without deliberately creating a second booking. Reuse the same idempotency key for the same intended reservation, instead of creating a fresh request identity after an uncertain response.

Will failed webhook deliveries be retried?

Yes. Failed deliveries retry with backoff beginning at five minutes, with at most eight attempts within a 24-hour delivery window. Inspect delivery response codes in the dashboard, and deduplicate notifications by their payload ID. Store delivery identifiers in your receiver so a later attempt doesn't create a second copy of an already-processed booking change.

Create your free booking link

Sign in with Google, create an event and share your link.

Create your free link