Quickstart
TattooAPI is live as a governed control plane. The first decision is which access lane you are in.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:The canonical public API host is
api.tattooapi.com. api.tattoo.co may remain as a marketplace/internal alias for tattoo.co-owned applications, but docs and SDKs should prefer api.tattooapi.com.1. Check Health
Use public liveness for basic availability:status: "ready" with publicWritesAllowed: false.
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. For internal beta reads, use the partner portal:- Sign in at
https://partners.tattoo.dev. - Select your approved organization.
- Create a docs playground key.
- Confirm the key is mapped by TattooAPI.
- Open the Mintlify playground on
https://docs.tattoo.devand run your first request.
401means the credential is missing or invalid.403means the credential is valid but has no active TattooAPI actor mapping for it.410means a legacy local API-key route is retired.
3. Search the Dataset
GET /search currently requires authenticated internal beta access.
4. List Studios
GET /studios is the current public discovery endpoint.
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:recordStatetells you if a record israw,normalized,curated,verified, ordeprecatedverificationStatustells you how much trust has been establishedlicenseStatusandconsentLeveltell you what kinds of downstream use are allowed
unmatched, phone_matched, review_required, and verified_by_operator describe review evidence only; they do not claim legal identity verification.
Next:
