Create and manage API keys

Which permission do I need

The Create a key form groups permissions by area, in the order used below. Tick the exact label a tool needs, and nothing more. One key can carry labels from more than one area, so a tool that reads cards and prepares drafts needs both.

Account covers your account details, payments and the activity log. Cards and statistics covers reading your cards and their statistics. Create and edit cards covers preparing card drafts, importing cards from a CSV file and publishing the cards you approved. Projects, Pixels, Domains and Teams cover those areas, and each of them has a read label plus a separate label for changes.

Managed-profile approval protects profile publication. Permissions to change projects, pixels, domains or teams authorize those account API operations directly, without a profile review. Give a tool those permissions only when it needs them.

• Read your account details: tick Read account details.
• Read your payments: tick Read payments.
• Read the activity log: tick Read the activity log.
• Read your cards and their content: tick Read cards.
• Read card statistics: tick Read card statistics. Your plan must also include analytics.
• Create cards and change their drafts: tick Create and edit cards (saved as drafts you approve).
• Send rows of people as an import: tick Import cards from CSV.
• Publish a card you approved: tick Publish cards you approved.
• Read projects: tick Read projects. To create, change or delete projects, also tick Create, change and delete projects.
• Read pixels: tick Read pixels. To create, change or delete pixels, also tick Create, change and delete pixels.
• Read your custom domains: tick Read domains. To add, change or delete custom domains, also tick Add, change and delete custom domains.
• Read teams and their members: tick Read teams and members. To manage teams, invitations and memberships, also tick Manage teams, invitations and memberships.

Reading the key list

Active keys are listed first and past keys are folded under Past keys. Each key shows the characters it starts with, its permissions and when it was last used, or Never used. Last used updates at most once a minute, so a busy tool does not change the time you see on every request.

Open View key details and revoke on a key to see its Created and Expires dates and to reach the revoke action.

Revoking a key

Open View key details and revoke, tick the confirmation that tools using the key will stop working, then choose Revoke key. Requests using the key fail immediately, so update the tool with a new key as soon as you can.

Revocation immediately prevents new requests and stops unfinished import rows and pending imported photos from being applied. Background cleanup records their cancellation in batches, so an import may take time to show Cancelled. Completed rows, saved drafts and published cards remain, and you can still act on an existing review. An operation already committed before revocation is not undone.

Expiry prevents new requests, but previously accepted imports and their photos can continue and still occupy import capacity. Revoke the key if you need to stop that unfinished work. Imports you submitted yourself in the dashboard are unaffected by a tool key being revoked.

Plans and availability

Professional includes the developer API, managed-profile API and MCP connections for AI assistants. Starter includes CSV profile import in the dashboard, but not API or MCP access. Custom plans keep their agreed permissions. If access is temporarily paused, the API keys page shows a pause notice; upgrading does not remove a site-wide pause.

Good ways to use this

• Create one key per tool and name it after the tool, so the review page and the key list always show you which tool did what.
• Give the smallest set of permissions that works, and choose the shortest validity that fits how the tool is used.
• Revoke keys you no longer use instead of waiting for them to expire.

Common questions