What is a scheduling API?
On this page
How does a scheduling API turn availability into a booking?
A scheduling API separates reading available times from creating an appointment. Your application first requests eligible starts for an event, then submits the selected start with the guest details required by the booking contract; the server decides whether it can accept that request.
Availability can change meanwhile. Treat the response as a set of choices to present, and keep the confirmation result as the point where your interface announces success.
A basic sequence looks like this:
- Read the event's supported durations and booking questions.
- Request available starts for the chosen duration and date range.
- Collect the guest's required details and selected start.
- Create the booking and display either confirmation or a recoverable error.
A scheduling API contract covers both its data format and permission rules. An endpoint address alone doesn't explain which credentials it accepts or which fields it requires.
What would a thirty-minute API booking look like?
A thirty-minute booking needs a full thirty-minute interval, not merely an available start label. Suppose an event offers 10:00 and 10:30 with no buffers: choosing 10:00 reserves an appointment ending at 10:30 only after the server accepts the creation request.
Keep the assumptions visible. If another person takes 10:00 before your request completes, your form should offer fresh availability instead of displaying an invented confirmation.
This example describes interface behavior. It isn't a production request snippet, and it deliberately omits credentials and payload fields that must come from the current API reference.
How is a scheduling API different from a webhook?
An API lets your application request data or an action, while a webhook notifies your application after an event occurs. A custom booking flow may use both: an API creates the appointment, then an event notification lets another system react to the accepted booking.
Direction matters here. Polling the booking list repeatedly is a different design from receiving a notification when something changes.
| Interface | Typical exchange |
|---|---|
| Scheduling API | Your application asks the scheduler for available starts |
| Booking webhook | The scheduler sends your endpoint an event notification |
The API and webhook feature explanation covers their roles together. The schedulers offering developer access comparison addresses product selection instead of API implementation.
Which booking actions does Barq Meet expose to developers?
Barq Meet provides a REST API and an OpenAPI description for reading events and slots, creating bookings, and managing supported booking changes. Use the published contract when building requests, because authentication and required fields vary with the operation.
Keep the contract close. We provide secret and publishable API keys with different permissions. Booking lists require a secret key; a publishable key has origin restrictions and additional protections for booking creation and management.
We also support an idempotency key for booking creation, allowing your server to retry the same intended request with the same key. That doesn't turn a new key into a duplicate-detection policy for your whole application.
We apply availability checks to API bookings too. Barq Meet connects to Google Calendar, so a custom front end won't add an Outlook calendar connection or payment processing through the booking API.
The scheduling definitions index explains neighboring terms. Read the included API access and account limits, then set up an account for a custom booking flow.
Frequently asked questions
Is an embed the same thing as a scheduling API?
No. An embed displays a booking interface inside a website; an API lets your code request data or perform supported actions. Choose the embed when you want the existing guest interface without building the booking screens yourself. Use an embed for a supplied booking interface and the API when your application needs to control the booking flow and handle its responses.
Can I put a secret API key in browser code?
No. Keep secret keys on a server you control because visitors can inspect browser code and requests. Barq Meet also provides publishable keys with origin restrictions, whose permitted operations and booking protections differ from server-side keys. Keep secret credentials on the server and check the documented authentication for each operation before exposing a booking control in a public application.
Will reading a slot reserve it for my application?
No. Reading availability shows what can be offered at that moment; it doesn't itself create an appointment. Submit the booking and handle a conflict response if another commitment has taken the time before confirmation completes. Submit the booking and inspect the result before showing a confirmed appointment, since another commitment can occupy the displayed interval before your request finishes.
Related pages
- Booking API and webhooks for your own application
Build with REST, OpenAPI and signed webhooks. Browser keys require allowed origins; server keys stay private. Default API access is 600 requests/minute.
- Scheduling apps with a free API and webhooks
Compare scheduling APIs and free webhooks without treating them as the same feature. Includes TidyCal, Cal.com and a Google Calendar booking API.
- Scheduling glossary: booking and calendar terms explained
Understand booking pages, events, free/busy and time-zone terms. Follow one 30-minute appointment through the scheduling vocabulary.
Create your free booking link
Sign in with Google, create an event and share your link.
Create your free link