- A personal API key acts as you, with your role and the repositories you can see. It stops working if you leave the team.
- A service account token belongs to the team, carries its own role, and sees every repository in the team. Use one for CI and other shared automation. See Service accounts.
API keys are available on Pro and Enterprise plans.
Create a key
1
Open API Keys
Go to Settings > API Keys and click Create API Key.
2
Name it
Keep API key selected for a personal key, and give it a descriptive
name, such as
Local scripts.3
Set an expiration
Choose 7, 30, 90, or 365 days. Gecko rejects an expired key with
401.4
Copy the key now
Gecko shows the full key value once, at creation. Copy and store it
securely; afterward only a masked preview is shown.
Use a key
Send the key either as a bearer token or in theX-API-Key header:
Manage and revoke
Keys are visible to the whole team. The API Keys table shows each key’s name, masked preview, who created it, creation date, last-used time, and expiration date. Service account tokens carry a Service account tag. Usage is logged per request, so last-used stays accurate. Delete a key to revoke it immediately. You can always delete your own keys; deleting a teammate’s requires theapi_keys.manage permission.