Retrieve your API key
MeetGeek authenticates with a static API key sent as a bearer token. The key lives on the MeetGeek API app under Integrations and never expires. Public API access is included on every plan, including the free Basic plan.
Sign in to MeetGeek
Sign in to your MeetGeek account.

Open Integrations
Open the integrations area of your workspace.
- Click Integrations under PRODUCTIVITY in the left-side navigation, or open the MeetGeek integrations page directly.

Open the MeetGeek API app
The Apps & Workflows page opens on the Apps tab.
- Stay on the Apps tab and find the MeetGeek API card — “Access meeting data programmatically via the MeetGeek public API”.
- Use the search box in the top right to filter for
MeetGeek APIif the card is not visible. - Click the card to open its settings panel.

Copy the API key
The settings panel opens on the right with the key already generated — there is nothing to create.
- Click the copy icon next to the API Key field.
- Paste the value into the API Key field in StackOne.
- The refresh icon beside it regenerates the key. Only use it if the current key is compromised — regenerating invalidates the old key and breaks any integration still using it.
- Leave Webhook URL and Secret Token empty. They are for MeetGeek’s own outbound webhooks and are not used by this connection.

Select your data region
API keys are region-specific. Each MeetGeek region issues its own keys, and a key only authenticates against the region it was generated in. In StackOne, set Data Region to the region your MeetGeek workspace is hosted in.
- Check the address you sign in to MeetGeek at. Workspaces opened at
app.meetgeek.aiare hosted in Europe. Workspaces opened atus.meetgeek.aiare hosted in the United States. - Default (Europe) sends requests to
api.meetgeek.ai, which routes to MeetGeek’s European data centre. Choose it for any workspace opened atapp.meetgeek.ai. - Europe sends requests to
api-eu.meetgeek.ai. Choose it only if you need to target the European endpoint explicitly. - United States sends requests to
api-us.meetgeek.ai. Choose it for any workspace opened atus.meetgeek.ai. - If the region does not match the key, MeetGeek rejects the key and the connection fails with an authentication error. Change Data Region and connect again — the API key itself does not need to change.
Link the Account
Connect
- Click Connect.
- If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider’s authorization flow.
- Once authorization is successful, you will see a confirmation popup.
Use Actions
Next Steps
Webhooks setup
Configure receiving Events for MeetGeek into StackOne.