Getting Started

From zero to first request.

tattoo.dev is a REST API and data platform for the tattoo industry. This guide walks you through the data model, credentials, your first call, and choosing the right builder path.

Use this as the implementation map once access is enabled.

What is tattoo.dev?

Tattoo-native data model

Artist profiles, healed-work portfolios, studio relationships, booking flows, trust signals, and messaging — structured for how the tattoo industry actually operates, not reverse-engineered from generic local business software.

REST API, JSON responses

Standard Bearer token auth, JSON request/response bodies, and versioned endpoints at api.tattooapi.com/v1. Full reference at docs.tattoo.dev.

Proven in production

tattoo.co, tattoo.agency, and TattooOS all run on this platform. The APIs handle real artists, studios, and clients every day — not theoretical.

Platform overview & data model

Get your API credentials

How access works

Start with docs.tattoo.dev — the quickstart and auth reference are there
API keys are scoped by environment: sandbox (testing) and live (production)
Sandbox is seeded with real-world data patterns — no fake lorem ipsum
Request production access via /contact when your integration is ready

Key format

// Sandbox
ttd_sandbox_xxxxxxxxxxxxxxxxxxxx

// Production
ttd_live_xxxxxxxxxxxxxxxxxxxx

Auth reference on docs.tattoo.dev

Your first request

JavaScript (fetch)

const res = await fetch(
  'https://api.tattooapi.com/v1/artists?city=las-vegas&limit=10',
  {
    headers: {
      'Authorization': 'Bearer ttd_sandbox_xxxxxxxxxxxxxxxxxxxx',
      'Content-Type': 'application/json'
    }
  }
);

const { data, meta } = await res.json();

cURL

curl 'https://api.tattooapi.com/v1/artists?city=las-vegas&limit=10' \
  -H 'Authorization: Bearer ttd_sandbox_xxxxxxxxxxxxxxxxxxxx' \
  -H 'Content-Type: application/json'

Response shape

{
  "data": [
    {
      "id": "art_01HXYZ",
      "name": "Maya Chen",
      "styles": ["blackwork", "geometric", "dotwork"],
      "studio": {
        "id": "std_01ABCD",
        "name": "Ink & Iron Las Vegas"
      },
      "location": { "city": "Las Vegas", "state": "NV" },
      "portfolio_count": 47,
      "trust_score": 0.94,
      "availability": "open"
    }
  ],
  "meta": { "total": 142, "page": 1, "per_page": 10 }
}

Illustrative of the data model — see docs.tattoo.dev for exact endpoints, schemas, and auth flows.

Choose your builder path

Marketplace builder

Discovery, listing, geo-indexed artist search, style taxonomy, and portfolio surfaces. GET /artists, GET /listings.

See use case

Studio software / SaaS

Booking flows, inquiry handling, deposit state, consent tracking, and studio operations. POST /bookings/inquiries.

See use case

AI or workflow tool

Pre-structured artist + studio data for AI models, LLM agents, and automation systems. Clean schemas, not scraped noise.

See use case

Independent dev / agency

Niche tools, studio sites, and booking automations. Use docs.tattoo.dev for implementation details and request access when ready.

See use case

MCP · Model Context Protocol

Connect Claude or any MCP client — the docs are live.

The tattoo.dev documentation is available as an MCP server. Connect your AI assistant directly to the API docs for real-time, context-aware implementation support — search endpoints, query schemas, and get answers from live documentation, not training data.

Claude Desktop config

{
  "mcpServers": {
    "tattoo": {
      "url": "https://docs.tattoo.dev/mcp"
    }
  }
}

What the MCP can do

Search across all API docs and guides
Query endpoint schemas and field definitions
Read auth, rate limit, and trust model docs
Access the full ontology reference

MCP setup guide on docs.tattoo.dev

Platform access - Reviewed paths only

The API layer for the tattoo industry.

Studio owners can book a Studio OS call, artists can join Artist OS, builders can request TattooAPI access, and technical readers can continue in docs.tattoo.dev.

Book or request access Open docs.tattoo.dev

Partnership access routes through reviewed conversations. Implementation detail lives on docs.tattoo.dev.

Platform Overview