Scheduling apps with a free API and webhooks
On this page
We build Barq Meet and ranked these options by what the pricing research actually establishes: API access, booking operations and webhook availability. Vendor pages were checked on 16 and 17 Nov 2026. Our free Calendly alternatives list compares the hosted pages if a custom integration isn't necessary.
Which scheduling APIs are confirmed free and which only confirm webhooks?
TidyCal explicitly confirms free API access; our booking API is included without a paid tier. Cal.com and Calendly confirm free webhooks in their pricing grids, but the pricing research doesn't establish the complete free API scope. Separate those claims before you prototype.
| Feature | Barq Meet | TidyCal | Cal.com | Calendly | Zcal |
|---|---|---|---|---|---|
| Ongoing free plan | Yes; fair use | Yes | Yes, 1 user | Yes | Yes |
| Types or links | Multiple events | Unlimited booking types | Unlimited links | 1 event type | Unlimited links |
| Calendars | Selected Google calendars | 1 readable | Unlimited | 1 connection | Unlimited accounts |
| Free API evidence | REST booking API + OpenAPI | API and MCP listed | Scope not established | Scope not established | Not stated |
| Free webhooks | Included, signed | Included | Included | Included | Paid |
| Reminders | Editable emails | Custom timing/content paid | Notifications; custom tier unclear | Paid | 1 automated email |
| Branding removal | Powered by badge stays visible | Pro | Teams | Standard+ | Paid |
Sources: TidyCal pricing, Cal.com pricing, Calendly pricing and Zcal pricing, as of 17 Nov 2026. "Scope not established" means this research doesn't answer the question; it doesn't mean the API is absent.
1. When is the Barq Meet API the first option to prototype?
Start with Barq Meet when you need your own interface to read event types and slots, then create or manage individual Google Calendar bookings. We publish REST operations with OpenAPI and signed booking webhooks. There isn't a paid API edition, though rate limits and generous fair-use controls apply.
Start with one appointment. We use the booking checks for the hosted page and the API, including a final availability check when the reservation is submitted. Your interface still needs to handle a slot becoming unavailable after it appeared in the date picker.
We separate a publishable browser key from a secret server key. Check the API and webhook feature guide for the key model and signing details before choosing the architecture. A secret belongs in your server environment, even when the frontend source is private today.
For a proposed client portal, show one 30-minute project review, request slots for a chosen date, then submit one selection. The webhook can update your internal appointment record after the booking changes. Two browser clicks mustn't become an assumption that the same slot can be reserved twice.
We connect Google Calendar and create Google Meet links, but don't collect payments or find collective availability across hosts. If your API project needs payment-before-booking or a panel interview, the missing scheduling function matters more than a zero API subscription price.
2. Is TidyCal the clearest verified free API alternative?
TidyCal has the clearest explicit free API statement among the researched competitors: its pricing page lists API, MCP and webhooks as free on every plan. Free also includes unlimited booking types (TidyCal pricing, as of 17 Nov 2026). That establishes access, not every operation's behavior.
Read the API documentation next. The pricing research is pricing research, so we aren't inventing endpoint names, token lifetimes or throughput limits. Before committing, test the operations you require and inspect the vendor's error and retry rules.
TidyCal Free reads one calendar, while automatic Zoom, Google Meet and Teams links require payment (TidyCal pricing, as of 17 Nov 2026). A custom interface doesn't remove those plan restrictions. If automatic conferencing is part of the spec, include it in the prototype.
Paid and package bookings are listed on Free, with a 1% platform fee on Stripe payments (pricing, as of 17 Nov 2026). That can make TidyCal the stronger starting point when your integration includes taking money, which we don't handle.
3. What does Cal.com confirm about free webhooks?
Cal.com's Free grid confirms webhooks, alongside custom booking questions and requires-confirmation controls. Free allows one user, unlimited links and unlimited calendars (Cal.com pricing, as of 17 Nov 2026). That makes it a candidate for connecting a hosted booking page to your own system.
Avoid extending the claim. The pricing checks doesn't establish the complete free API surface, quotas or whether your intended write operation is included. We haven't presented webhooks as proof that a custom booking frontend can use every operation without another agreement. Read how booking notifications reach another system before treating webhook delivery as proof that a downstream customer record has been updated.
Branding removal starts on Teams, and the page's notification claims conflict between its grid and plan card (Cal.com pricing, as of 17 Nov 2026). Test hosted-page presentation and messages as well as the webhook payload if the client will interact with that page.
4. Can Calendly Free send webhooks even though reminders are paid?
Yes: Calendly's rechecked pricing grid includes webhooks on Free, while automated reminders start on Standard. Free still has one event type and one calendar connection (Calendly pricing, as of 17 Nov 2026). Those are independent allowances and shouldn't be collapsed into one automation verdict.
One event type may suffice. An internal process that reacts when a single consultation is booked has a different requirement from a marketplace that creates several appointment offers and calendars. Establish the business operation before comparing developer plan names.
The pricing research doesn't establish the full free booking API scope or API rate limits, so we leave those unresolved. Standard is $10 per seat per month billed yearly or $12 billed monthly on Calendly's pricing page, as of 17 Nov 2026; that price alone doesn't answer an API entitlement question.
How should you test a free scheduling API before building around it?
Test booking, conflict handling and event delivery before you build the complete interface. Expect retries. A network response can disappear even when the server completed an operation, and webhook delivery can happen more than once, so your application needs a defined recovery path instead of a second blind reservation. The scheduling-API definition distinguishes a supplied embed from an application that must handle availability and booking responses itself. For a custom guest interface, build the booking flow around the API's actual responses instead of treating returned slots as held reservations.
- Read one event type and fetch slots for a narrow date window.
- Create a booking with the documented retry mechanism.
- Attempt the same time after it is occupied and inspect the error.
- Cancel or reschedule the booking and inspect the resulting webhook.
- Store processed event identifiers so a repeated delivery doesn't create repeated work.
For Barq Meet, use the documented idempotency mechanism for booking retries and verify webhook signatures over the original bytes. We haven't pasted guessed endpoints here. Follow the published API reference from the linked feature guide when implementing.
Which tools should stay out of a free-webhook shortlist?
Zcal's webhooks are paid, so its generous hosted Free page doesn't meet a requirement for zero-cost event delivery. That split is verified on Zcal pricing, as of 17 Nov 2026. It can still work without integration.
We left developer products without verified free API terms out, instead of treating an SDK or an embed as equivalent access. If the Google Calendar scope works for your project, review our API usage terms and create an account for a booking prototype. Prove one booking before designing the whole portal.
Frequently asked questions
Can I put a secret booking key in a browser app?
No. Keep a secret Barq Meet API key on your server and read it from an environment variable. For browser access, use the supported publishable-key route with allowed origins and the documented booking operations. Keep server credentials on your backend and send only the publishable key intended for browser requests to the client.
Does a webhook create the calendar booking?
No. A webhook reports something that happened; it isn't the command that reserves a slot. Submit the booking through the supported booking route, then use the resulting event to update your own records. Create the booking through the booking endpoint, then use the delivered notification to update the other system's record.
Should I build a custom interface before testing availability?
No. Test one event and its available slots first, then one complete booking. That small path exposes calendar and error-handling requirements before you spend time on a date picker that can't explain an unavailable slot. Try a real conflict and a retried request so the interface design accounts for rejected or uncertain booking attempts.
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.
- Free Calendly alternatives: six plans compared (2026)
Compare six free Calendly alternatives by event types, calendars, reminders and branding. Calendly Free allows one event type and one calendar.
- Free scheduling, with every feature included
Get booking pages, Google Calendar and Meet, reminders, branding controls, embeds and API access for $0. No card or paid plan.
- What is a booking webhook?
A booking webhook sends an event notification to your endpoint. Learn signed delivery, retries and duplicate handling with a one-booking example.
- What is a scheduling API?
A scheduling API lets software read available times and manage bookings. See a 30-minute example, key permissions and the difference from webhooks.
- How to build a custom booking page with a scheduling API
Build a custom booking interface with REST and OpenAPI. Read slots, create appointments, protect API keys and handle stale times and approval states.
Create your free booking link
Sign in with Google, create an event and share your link.
Create your free link