Why Embed Meet.bot
Building scheduling into your product typically means months of development, OAuth app reviews, and ongoing maintenance. Meet.bot gives you a production-ready scheduling layer that your users can start using on day one.
No App Setup Required
Your users don't need to create Google or Microsoft apps. Meet.bot handles all calendar OAuth, so there are no approval cycles or complex configuration steps for your team or your customers.
Same-Day Launch
Get your partner token and start creating scheduling pages for your users via API immediately. No lengthy onboarding process or integration review required.
Complete Solution
Unlike raw calendar APIs, Meet.bot gives you scheduling pages, availability management, booking confirmation, and calendar sync out of the box. Ship a full scheduling experience, not just calendar access.
Pay Per Meeting
Only pay when meetings are booked. No per-user fees or per-connection charges, so your costs scale predictably with your customer base.
How It Works
Integrating Meet.bot scheduling into your product takes three steps. No complex setup, no app store approvals.
Get your partner token
Contact us to receive your partner API credentials. We will set up your partner account with a dedicated token, shared secret for webhook verification, and your webhook URL.
Create scheduling pages
Use the API to create and configure scheduling pages for your users. Set meeting durations, availability windows, and customize the booking experience to match your product.
Receive booking events
Get real-time webhook notifications when meetings are booked. Each webhook payload is JWT-signed so you can verify authenticity and sync bookings into your system.
Meet.bot vs Calendar APIs
Raw calendar APIs like Nylas give you access to calendar data, but you still need to build the scheduling experience yourself. Meet.bot provides the complete solution. See our detailed comparisons: Meet.bot vs Nylas and Meet.bot vs Cronofy.
| Feature | Meet.bot | Raw Calendar API (Nylas, etc.) |
|---|---|---|
| Scheduling pages | Included | Build yourself |
| Availability management | Included | Build yourself |
| Booking UI | Included | Build yourself |
| Calendar sync | Included | Included |
| OAuth app setup | Not required | Required |
| Time to launch | Same day | Weeks/months |
| Pricing | Per meeting | Per user/connection |
Technical Details
Meet.bot's partner API is built for straightforward integration. Here is what you need to know about the technical side.
Partner Tokens
Each partner integration receives dedicated API tokens. Use your partner token to authenticate API requests for creating scheduling pages, managing availability, and booking meetings on behalf of your users. When a user connects their calendar, you receive a user-specific token via webhook to make API calls on their behalf.
Webhooks
All webhook payloads are delivered as JWT-signed POST requests to your configured endpoint. You verify the signature using your shared_secret to ensure the payload is authentic. Two event types are available:
booking_received: Fired when a meeting is booked through one of your users' scheduling pagespartner_token_created: Fired when a new user connects their calendar and a user-specific API token is generated
API Endpoints
The REST API covers the full scheduling lifecycle: create pages, check availability, and book meetings. All endpoints accept and return JSON with Bearer token authentication.
POST /v1/page-create: Create a new scheduling page for a userGET /v1/page-config: Retrieve page configuration and settingsGET /v1/slots: Get available time slots for a scheduling pagePOST /v1/book: Book a meeting in a specific time slotGET /v1/pages: List all scheduling pages for a user
For complete API documentation with request parameters, response schemas, and code examples, see the developer docs. To learn more about the partner program and integration steps, visit the partner page.
Frequently Asked Questions
Nylas provides raw calendar API access. Meet.bot is a complete scheduling solution with scheduling pages, availability management, and booking UI included. You get a working product, not building blocks. There is no need to build and maintain your own scheduling frontend or availability logic.
Yes, scheduling pages can be customized with your branding, colors, and company domain. You can pass styling parameters like primary_color and show_background when embedding pages, or build your own booking UI entirely using the API.
We send booking_received when a meeting is booked and partner_token_created when a new user token is set up. All webhooks are JWT-signed for security, and you verify them using the shared secret provided during partner onboarding.
You only pay for meetings that are actually booked through the platform. There are no per-user or per-connection fees, making your costs predictable and directly tied to the value your users receive. This model scales naturally as your customer base grows.
Users need to connect their calendar through Meet.bot, but they don't need to set up any Google or Microsoft apps. Meet.bot handles all OAuth flows. Your users simply click a connect button and authorize their calendar. No developer console setup or app approval required on their end.
Scales With Your Business
Per-meeting pricing means your costs grow only when your users book meetings. No per-seat minimums, no connection fees, and no surprises as you scale.
