TattooBooking API

Build integrations against the TattooBooking platform — sync appointments, leads, clients, payments, and form submissions to anything your studio uses.

This guide is for developers building against the platform. If you're looking to connect a no-code tool, jump straight to the recipes.

Three ways to integrate

REST API. Cursor-paginated CRUD over 13 resources. Auth by API key or OAuth bearer token. See the reference →
Webhooks. Subscribe an HTTPS endpoint to one or more of the 32 public event types. HMAC-signed, retried for ~72 hours. Learn more →
Zapier. Official published app — pipe events into 5,000+ tools without writing code. Browse recipes →

If this is your first time

Start with the Quickstart — generate a key, make your first call, and receive your first webhook delivery in under 10 minutes.

What you should read next

Authentication — API keys vs OAuth, when to use which.
Errors — RFC 9457 problem+json shape, codes you'll see.
Idempotency — safely retry mutations.
Rate limits — tier limits, 429 responses, backoff.
Webhooks — events, signature verification, retry policy.

Stability & versioning

Every endpoint is on /v1/. We follow an additive-only versioning policy — new fields and new endpoints get added without bumping the major version, so your integration keeps working as we ship features. Breaking changes (renames, removals, behavior changes) only happen on a major-version bump (/v2/) with a published deprecation timeline. See Versioning for the full policy.