Groupilot Docs

API keys

Create, name, scope and revoke API keys from the Integrations page, and read the call log.

Create a key

Open Settings, Integrations

The page lists the keys of the current project with their name, scopes, creation date and last use.

Choose a name and the scopes

Name it after the tool that will use it. Tick read, write, send as needed. See Authentication and scopes.

Copy the key

It is shown once, in full. Store it in the secret store of your tool. The page later shows only the first characters, to help you recognise it.

Limits

  • 5 active keys per project.
  • A key belongs to one project. For several WhatsApp numbers, create a key in each project.
  • An optional expiry date can be set at creation.

Revoke

Choose Revoke next to the key. Calls with that key fail with 401 within a minute. Revocation cannot be undone: create a new key if needed.

Call log

The Integrations page shows the last 50 API calls of the project: date, method, path, HTTP status, duration, and which key was used. Request and response bodies are never stored.

Keys for an agency

An agency manages one project per client, from the same login. Keys are per project, so a tool that serves several clients holds one key per client. If that is a burden, look at Connect OAuth, where the client authorises your platform once.

On this page