Integrations
Inkdesk API for tattoo shops and agencies
Inkdesk exposes a public HTTP API under /api/v1 for catalog, availability, estimates, bookings, deposit intents, portfolio, and related client operations. Browse the contract at /api/v1/openapi. Authenticate with hashed api_keys: sk_ on the server, pk_ in the browser with origin allowlists. Register outbound webhooks to receive HMAC-signed events (X-Inkdesk-Signature) for Zapier, Make, or your own workers. The booking widget and Connect wizard sit on the same platform. Inkdesk is $50 per shop per month per shop tenant.
What can you build with /api/v1?
Agencies build custom book flows on Webflow, Next.js, or native apps while Inkdesk remains the multi-tenant CRM: appointment state machine, Stripe Connect deposits, reminders, waitlist, consent, and cabinet. Typical reads: services/artists catalog, slot availability, price estimates. Typical writes: create bookings, create deposit intents, portfolio and reference uploads via presign where enabled.
OpenAPI at /api/v1/openapi is the machine-readable source for paths and schemas. SDKs exist under packages/sdk-* (@inkdesk/sdk on npm and counterparts on Composer/PyPI) for typed clients and webhook verification helpers.
RLS and tenant isolation still apply—keys are scoped to the shop. Do not share sk_ keys in front-end bundles or WordPress options.
Webhooks, Zapier, and Make
Register webhook endpoints via POST /api/v1/webhooks (see OpenAPI). Deliveries are HMAC-signed; verify X-Inkdesk-Signature with the SDK verifyWebhook helpers before trusting the body.
Zapier and Make connect through those webhooks—scaffolds live in integrations/zapier and integrations/make. Use them to notify Slack, update a sheet, or trigger CRM side effects when a deposit pays or a booking confirms.
Domain events inside Inkdesk also fan out to notification and calendar workers; webhooks are the external mirror for your automation stack.
Widget vs API vs hosted page
Hosted /{salon}/book: zero engineering. Script/iframe widget: drop-in UI on WordPress, Wix, Squarespace, Webflow, Shopify, or HTML. API: full control of UI with Inkdesk as backend. Most tattoo shops start with hosted or widget; agencies graduate specific clients to API without migrating shops off Inkdesk.
- 1Plugin / blockWordPress · Download plugin → Generate connect code
- 2App or snippetShopify/Wix Add to… · or Create snippet for Code/Embed
- 3Hosted book pageNo website · Create hosted link + QR → /{salon}/book
Site connections and the Connect wizard issue embed materials so owners are not copying sk_ keys into CMS fields. Browser pk_ keys remain origin-allowlisted.
Subscription stays $50/shop/month whether you embed or API-integrate—the API is part of the platform, not a separate SKU in the marketing price.
Security basics
Deposit amounts for PaymentIntents are computed server-side from shop rules—clients cannot invent charge totals through the public book path. Webhooks that confirm payment check PaymentIntent identity and amount. Stub deposit confirm is disabled when live Stripe keys / production hardening apply.
Rotate keys from the cabinet if a pk_ leaks into a public repo. Prefer connect codes for WordPress instead of hand-pasted secrets.
FAQ
Where is the OpenAPI document?
On the app host at /api/v1/openapi.
Can Zapier book appointments?
Automation typically listens to Inkdesk webhooks for booking and deposit events. Building Zapier actions that create bookings depends on your Zapier integration configuration; webhooks are the supported external event path.
Is the API available on the $50 plan?
Yes. The public API and webhook registration are part of the shop platform. Standard Stripe fees still apply on card charges.
Widget or API for a normal street shop?
Start with the Connect wizard embed or hosted book page. Use the API when you have an agency building a custom front.
Inkdesk is $50 per shop per month — one shop subscription, not a pile of add-ons. Start a free trial or open the live demo with sample data. No credit card required to look around.