Personal Access Token (API Key)
Where to get your meetergo API key: generate a Personal Access Token to connect meetergo Log, a phone assistant or your own app to the meetergo API. The Zapier and Make apps sign in with your account instead.
meetergo allows you to easily generate a personal access token that you can use to authenticate with the meetergo API.
If a tool is asking you for a "meetergo API key" or "API token", this is almost always what it means. Personal Access Token is the name meetergo uses for it.
Personal Access Tokens are available on every plan, including Free.
Your personal access token should not be shared with anyone outside your organization.
Which credential do I need?
meetergo has two different credentials, and only one of them is created on the Integrations page. Pick the row that describes you:
| You want to... | Use | Where |
|---|---|---|
| Connect a tool to your own meetergo account (meetergo Log, a phone/voice assistant such as Placetel or IONOS, a script, a Webhooks by Zapier or HTTP step that calls the meetergo API) | Personal Access Token — this article | Integrations & Apps |
| Build a product on top of meetergo that provisions and manages other people's accounts | Platform API key (ak_live:...) | Admin → API, and it needs a separate API Platform plan |
The official Zapier and Make apps do not take a token at all. You connect them by signing in with your meetergo account inside Zapier or Make, see Connect Zapier and Make with meetergo. A Personal Access Token only comes into play when you call the meetergo API yourself from one of those platforms.
If you are a meetergo customer wiring up one of your own tools, you want a Personal Access Token. A Platform API key will not work for that: it is company-wide, requires an extra x-meetergo-api-user-id header on every request, and is only available on the API Platform plan. See API Documentation Overview if you really do need the Platform API.
Creating a Personal Access Token
Follow these steps to create a personal access token and use it with our API:
- Log into your meetergo account and navigate to Integrations & Apps
- Find the "Personal Access Tokens" section
- Click "Create Token" to generate a new access token
To create your token, you need to give it a unique name. You can optionally set an expiration date.
Make sure to copy the token to a secure location, as it cannot be displayed again after creation.
Usage
To access protected resources, your personal access token (copied in the previous step) must be provided as a Bearer token in the Authorization header of your request.
Example header:
Authorization: Bearer your_token_here
For more detailed instructions on using the API endpoints, refer to our API documentation.
What the token can access
A Personal Access Token acts as you. API calls behave exactly like actions you perform in the meetergo dashboard, with your role and permissions:
- As a regular member, the token can manage your own meeting types, availability, and bookings.
- As an admin, the token can also read and manage data across your workspace, for example listing users or retrieving other users' appointments.
The token cannot create, update, or delete users, and it cannot act on behalf of another user. These operations require the meetergo API Platform. You can find details in the developer documentation.
If the token's owner is removed from the workspace, the token stops working. For integrations your organization depends on, create the token from a shared admin account (for example integrations@yourcompany.com).
Security
For security reasons, the token is not stored on our servers. This means you cannot view your token after it has been issued.
Additionally, we recommend setting an expiration date for your tokens. After a token expires, it can no longer be used to authenticate with the API.
If you want to revoke one of your tokens, you can do so using the "Revoke" button next to the token. Once you revoke a token, it can no longer be used to authenticate with the API.
Related Articles
Was this article helpful?
Let us know if this article answered your questions.