Skip to main content
A Personal Access Token (PAT) is the fastest way to use the meetergo API. It authenticates as you: every API call behaves exactly as if you performed the action in the dashboard, with your role and permissions. No user context headers, no platform setup.
Available on every plan, including Free. Create yours at Integrations → API.

​
Limit a token to capabilities

A token can be limited to the parts of the API an integration needs. Pick the capabilities when creating it; a limited token gets 403 on everything else, with a message naming the capability it lacks. A token created without any capability selected has full access.

​
What a PAT can do

A PAT inherits the permissions of the user who created it. It is not limited to that user’s own data:
  • A regular member’s PAT manages that member’s meeting types, availability, bookings, and contacts.
  • An admin’s PAT additionally reaches workspace-wide data, just like an admin in the dashboard.
For example, an admin’s PAT can enumerate the workspace and pull every user’s appointments:
This makes an admin PAT sufficient for most workspace integrations: syncing bookings into a CRM or data warehouse, building reports across your team, or migrating from another scheduling tool.

​
What a PAT can’t do

A few operations are reserved for Platform API Keys, regardless of your role:
  • Act on behalf of another user. The x-meetergo-api-user-id header only works with a Platform API Key. If a PAT request carries that header for another user, it is rejected with 403. A PAT always acts as its owner; org-wide access works through your admin role and query parameters (like userId above), not through impersonation.
  • Manage the user lifecycle. Creating, updating, or deleting users via the API requires a Platform API Key. Manage workspace members in the dashboard instead.
  • Manage credentials. A PAT cannot create or revoke other PATs or API keys, and cannot trigger GDPR exports.
If you are building a product on top of meetergo (provisioning users for your own customers, white-labeling), you want the API Platform plan instead.

​
Setting up an organization integration

A PAT belongs to the user who created it. If that user is removed from the workspace, the token stops working. For integrations your organization depends on:
  1. Create (or designate) a stable admin account with a role address, e.g. integrations@yourcompany.com.
  2. Give it admin permissions.
  3. Create the PAT from that account and store it in your secrets manager.
This keeps the integration independent of any individual employee.
The token owner counts as a regular workspace seat. There is currently no separate non-billable service account type.

​
Token lifecycle

  • Tokens are shown once at creation. Store them securely.
  • You can optionally set an expiration date; rotate before expiry.
  • Revoke a token any time at Integrations → API.
  • If the owning user is removed from the workspace, their tokens stop working immediately. Create a replacement token from another admin account.

​
Common starting points

API Reference

Endpoints for bookings, meeting types, availability, and users

Webhooks

React to bookings and cancellations in real time

CRM Sync Recipe

Push booking data into your CRM

MCP Server

Use the API from AI assistants