Skip to main content

Quickstart

Start with a public studio read, then add approved credentials for authenticated endpoints.

What You Can Do Today

Public writes are blocked. Private workers cannot publish public surfaces, mutate canonical records, or bypass human review.

Base URL

Use the canonical public API base URL:
Resource reads require api-version=2026-07-01-preview. Health checks are unversioned. Owner reads use explicit /api/v1/me/* paths; do not add /api/v1 to this base URL.

1. Check Health

Use public liveness for basic availability:
Expected shape:
Use production readiness before relying on intake, private worker, or approved portfolio workflows:
Inspect the returned status: ready, degraded, or blocked. A successful health check does not prove that a complete portfolio workflow is ready.

2. Get Access

Public users do not need auth for health or studio discovery. Authenticated internal beta access uses approved partner credentials. Team members use bearer tokens, and machine or private worker tools use partner API keys.
Legacy registration and login routes are not available for onboarding. Get approved credentials through the partner portal.
For authenticated beta reads, use the partner portal:
  1. Sign in at https://partners.tattoo.dev.
  2. Select your approved organization.
  3. Create a key with the permissions your integration needs.
  4. Confirm the key is mapped by TattooAPI.
  5. Open the Mintlify playground on https://docs.tattoo.dev and run your first request.
For human sessions, send:
For machine, server, SDK, and private worker calls, prefer:
Response semantics are intentionally simple:
  • 401 means the credential is missing or invalid.
  • 403 means the credential lacks an active TattooAPI actor mapping, a required permission, or access to the requested resource.
  • 410 means a legacy local API-key route is retired.

3. Search the Dataset

GET /search currently requires authenticated internal beta access.
The response uses a success wrapper:

4. List Studios

GET /studios is the current public discovery endpoint.
Unlike search, the current studios endpoint still uses the legacy paginated wrapper:

5. Understand Trust

Before you build on top of the current data, load the trust model:
  • recordState tells you if a record is raw, normalized, curated, verified, or deprecated
  • verificationStatus tells you how much trust has been established
  • licenseStatus and consentLevel tell you what kinds of downstream use are allowed
For portfolio intake, identity evidence is not KYC. unmatched, phone_matched, review_required, and verified_by_operator describe review evidence only; they do not claim legal identity verification. Next: