Your users don't create Google or Microsoft apps. They add a "Connect with Meetbot" button, connect an existing account or sign up in two clicks, and manage everything from your product. No approval cycles or complex OAuth flows.

Go live when you want. Request a partner token, add the connect URL, and receive connection tokens and booking notifications via webhook. No long integration or approval waits.

Use our solution entirely via API, or use the scheduling pages we provide. Embed pages with optional styling (?show_background=0&primary_color=hex), or build your own UI with Get Slots and Book endpoints. You choose how much of the experience you build.

Unlike Nylas, Meet.bot is a complete scheduling solution, not just a calendar API. Your users get scheduling pages, availability management, and calendar sync out of the box. No Google or Microsoft app setup required.

Pay per meeting booked, not per user or API call. Scale your user base without scaling your costs.

Compare in detail: Meet.bot vs Nylas · Meet.bot vs Cronofy

Want a deeper look at embedding scheduling? See our Embed Scheduling page.

1. Sign up at meet.bot/signup and request a partner token (support ticket or hello@meet.bot).

2. Share: partner name, short ID (url-friendly), short description, logo, and webhook URL for connection tokens and booking notifications.

3. You receive a shared_secret to verify the Bearer JWT on webhook requests.

4. Add a "Connect with Meetbot" button linking to https://meet.bot/partner/{short_id}/connect?partner_user_id={your_unique_user_id}. Optionally add redirect_url to send users back to your app after connection. We recommend opening in a new tab.

5. When a user connects, your webhook receives a partner_token_created event with the token (API token for that user). Store it to call the API on their behalf.

6. Use the API at meet.bot/api: list pages (Get Pages), send contacts to page URLs or embed with our widget, or build your own flow with Get Slots and Book. Create and manage pages via API (page-create, page-config) or send users to meet.bot/pages.

7. Bookings trigger a booking_received webhook so you can sync meetings with your system.