API keys¶
API keys let external systems authenticate with Stackify without a user session. Each key is scoped to a workspace.
Create an API key¶
- Go to Settings → Integrations → API keys.
- Click Create API key.
- Enter a name (e.g. "Zapier integration" or "n8n workflow").
- Choose a permission scope:
- Read — can only read cards, fields, and records
- Read & Write — can read and write records; create and update cards and fields
- Click Create.
The full key is displayed once — copy it now and store it securely. Only a hash of the key is stored in Stackify; the full key cannot be retrieved later.
API keys look like this:
Use an API key¶
Include the key in the Authorization header of every API request:
See the REST API reference for endpoint details.
Manage API keys¶
From Settings → Integrations → API keys you can:
- Rename a key to help identify where it's used.
- Revoke a key immediately. Any requests using a revoked key will receive a
401 Unauthorizedresponse.
Treat keys like passwords
API keys grant access to your workspace data. Do not commit them to source control or share them in chat. Use environment variables or a secrets manager instead.
Key scopes¶
| Scope | Allowed operations |
|---|---|
read | GET on any resource |
write | GET, POST, PATCH, DELETE on cards, fields, and records |
Keys with only read scope cannot create, update, or delete anything.