Skip to main content

Current API Surface Map

TattooAPI is in a conservative public-read phase. The runtime has more route files than the promoted public surface, but only a small set should be treated as supported product API today.
This page is generated by npm run generate:mintlify-current-api-surface. Do not hand-edit route posture here; update the source contracts and rerun the generator.

Canonical Hosts

Public No-Auth Reads

These endpoints are the promoted public product surface today. Public studio writes are blocked.

Existing Public Ingress That Is Not New Product Surface

Some legacy or infrastructure routes are reachable without the authenticated beta flow. They should not be confused with the promoted public API roadmap. The current access model keeps these legacy paths from becoming the promoted team, owner, or private-worker auth model.

Authenticated Internal Beta Reads

These routes require approved credentials plus an active TattooAPI actor mapping. These routes exist so internal SDKs, private tools, and early operator workflows can test real read envelopes without widening the public product surface.

Blocked-Write Runtime Read Families

Several noun families have useful runtime-backed reads while public writes stay blocked. Two booking route families still have mixed runtime-read and legacy-write posture. They are not promoted as public write APIs and should not be used as the pattern for new route families.

Owner-Scoped Creative Beta

These routes require approved credentials plus owner mapping to the relevant studio or artist scope. Owner creative writes are contract-gated. POST, PUT, PATCH, and DELETE return owner-write-gated boundary responses until governed owner mutation contracts are promoted.

Internal-Only Infrastructure

These are not public API products.

Blocked Or Deprecated

Runtime Route Inventory

This inventory is not the same thing as the promoted public surface. It is included so documentation drift is visible.

How To Build Against This

  • Use public no-auth reads for public studio discovery and uptime checks.
  • Use authenticated internal beta routes for team and SDK experiments.
  • Use owner routes only when the caller maps to the owning studio or artist.
  • Treat source-pack, private worker, and runtime admin surfaces as internal infrastructure.
  • Do not build product UX that assumes public writes, public compliance claims, public GraphQL, or public SEO pages are live.
See API Access Model for projection and ownership rules.