Resources

tattoo.dev is the developer home for TattooAPI.

Use it to learn the tattoo-native primitives, read API references, understand auth and review boundaries, explore platform guides, and request access for the product surface you are building.

Representative API call

What a request looks like

// Representative — see docs.tattoo.dev 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.tattoo.dev. This is illustrative of the model, not a production endpoint.

Portfolio proof

The category should be visible in the system.

Not as loud decoration. As proof that the infrastructure is grounded in real artists, studios, clients, and the visual language they move through every day.

Detailed botanical forearm piece featuring hibiscus flowers and foliage in black and grey

Real input media

Hibiscus Flower Forearm Tattoo by Mike Shapiro

Hibiscus Flower Forearm Tattoo
Traditional Japanese dragon forearm piece featuring detailed scales, flames, and ornamental elements in black and grey.
Japanese Dragon Forearm Tattoo
Bold traditional calf piece featuring intertwined wolf and ram heads with classic bold linework and limited color palette
Wolf Ram Traditional Calf Tattoo
Detailed Polynesian tribal piece featuring traditional geometric patterns and motifs on the calf.
Polynesian Tribal Calf Tattoo

Canonical Reference

The canonical implementation reference lives on docs.tattoo.dev

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.