🆕 Personal access tokens (PATs) replace the personal API key

📢 Info & Announcements
1

Until now, every Tape user had one personal API key.
It had access to everything your Tape user could access across workspaces and apps. Changing that meant resetting the key and updating every integration using it.

You can now create as many personal access tokens (PATs) as you need, each with its own access and capabilities.

A personal access token lets you access the Tape API from scripts, tools and AI assistants. It uses your Tape user permissions, while you decide which workspaces, apps, and capabilities that token can access. A token can never have more access than you have in Tape.

:sparkles: Control what each token can access and do

  • Content access
    Choose ALL, or limit access to specific workspaces and apps.
  • Capabilities
    Choose what the token is allowed to do. Capabilities are grouped by Organization and Workspaces, for example Read workspaces, Edit workspaces, and Manage members. A token can only receive capabilities your Tape user already has.

:books: How to create a personal access token

  1. Click your avatar in the top-right corner
  2. Open Preferences
  3. Go to Developer
  4. Click New token
  5. Give it a name, then choose Content access and Capabilities
  6. Click Create token

Your new token starts with tape_pat_

:bulb: The token appears once

Tape shows your token only once, right after you create it. Copy and store it securely before closing the dialog. You won’t be able to view it again.

For security, Tape never stores a readable copy of your token. That’s why it can only be shown once. If you lose it, revoke it and create a new one.

:lock: Security best practices

Keep PATs as secure as passwords:

  • Store PATs in environment variables or a secret manager.
  • Do not commit PATs to source control.
  • Use a separate PAT per script, tool, or environment so you can revoke one token without breaking unrelated workflows.
  • Grant only the capabilities the workflow needs.
  • Revoke tokens you no longer use.
  • Select only the workspaces and apps the integration needs.

:repeat: What happens to your current API key

Your existing API key keeps working. You’ll now find it under Preferences → Developer, with ALL content access and ALL capabilities.

You can still copy your existing API key from the ••• menu. Personal access tokens, however, are shown only once when created.

We recommend replacing your old API key over time. Create a separate token for each integration, give it only the workspaces, apps, and capabilities it needs, then delete the old key. If one token is ever exposed, you can revoke only that token while everything else keeps running.

For full details, see developer API docs ➔ Personal Access Tokens

4 Likes
2

This is a welcome change. Can use API keys for granular access. Good one Team!

2 Likes