Skip to content

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

  1. Go to SettingsIntegrationsAPI keys.
  2. Click Create API key.
  3. Enter a name (e.g. "Zapier integration" or "n8n workflow").
  4. Choose a permission scope:
  5. Read — can only read cards, fields, and records
  6. Read & Write — can read and write records; create and update cards and fields
  7. 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:

tvk_live_a1b2c3d4e5f6...

Use an API key

Include the key in the Authorization header of every API request:

Authorization: Bearer tvk_live_YOUR_KEY

See the REST API reference for endpoint details.

Manage API keys

From SettingsIntegrationsAPI 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 Unauthorized response.

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.