Skip to main content

​
Get Access

Sign in at partners.tattoo.dev, select your approved organization, and create a key with the permissions your application needs. Your credential must have an active TattooAPI actor mapping before authenticated requests can succeed. Health and public studio reads do not require a key.

​
Request Headers

Server applications use a partner API key:
Approved human sessions use Authorization: Bearer YOUR_ACCESS_TOKEN. Follow the individual endpoint’s credential requirements; the two credential types are not interchangeable on every route. The partner-key path uses API-key authentication. It does not use OAuth client credentials for this path.

​
Permissions

Request only the permissions needed by your integration: Permissions do not override organization, artist, or studio scope. Submission access does not permit approval or public publishing. The restricted portfolio_intake:stage_cross_tenant capability is assigned only to explicitly approved service integrations, not self-service keys.

​
Errors

​
Docs Playground

The docs playground can use approved access from your partner session. Sign in to the correct organization and create a docs playground key before sending an authenticated request. Keep private keys on your server. Never put API key secret values in Mintlify docs, git, screenshots, or public examples. TattooAPI stores only non-secret credential identity metadata in actor mappings. See API Keys for key-management behavior and API Access Model for owner and submission boundaries.