Resources
Everything you need to build on Tattoo API.
Start with the docs for implementation detail, or explore platform guides and builder education for context on what to build and why.
Start Here
Quickstart Guide
End-to-end guide for getting started with Tattoo API authentication and your first request.
API Reference
Full endpoint reference with request/response schemas for every capability group.
Authentication
API key setup, OAuth flows, scopes, and environment separation for sandbox vs. live.
Platform Guides
What to build: positioning, use cases, and product-level implementation recommendations.
Ecosystem Context
How tattoo.co, tattoo.agency, and TattooOS relate to the API and each other.
Builder Education
Patterns and mental models for studio software, marketplace, and AI tool builders.
Representative API call
What a request looks like
// Representative — see docs.tattooapi.com for actual endpoints
const res = await fetch('https://api.tattooapi.com/v1/artists?city=los-angeles', {
headers: {
'Authorization': 'Bearer <YOUR_API_KEY>',
'Content-Type': 'application/json'
}
});
const { data } = await res.json();
// data → [ { id, name, styles, studio, location, portfolio, ... } ]Endpoints, schemas, and auth detail live on docs.tattooapi.com. This is illustrative of the model, not a production endpoint.
What type of builder are you?
Route into the docs path that matches your product.
Marketplace builders
Discovery, listing, trust, and portfolio primitives for tattoo-native consumer products.
Studio software
Booking, portfolio, reputation, and operational workflows for studio management products.
AI / workflow tools
Messaging, inquiry, portfolio, and trust signals for AI agents and automation systems.
Canonical Reference
The canonical implementation reference lives on docs.tattooapi.com
Endpoints, authentication, request schemas, response shapes, SDKs, and sandbox setup are all on the docs subdomain. This site is for platform positioning and access conversations.