Who this is for: studio owners, and the developers who build for them · Plan: Premium, switched on per studio on request · Product: Podyx V2
The Podyx API lets you build your own customer-facing booking experience, or connect your own systems, on top of Podyx. Your website or app handles the look and the flow; Podyx stays the source of truth for your catalog, availability, prices, clients, bookings and payments.
This article is the studio-side view: what the API is for, how to get it, and what changes for your team once an integration is live. The technical detail your developer needs lives in the Podyx API developer guides.
ℹ️ The API is a Premium plan feature, and it is switched on per studio on request. It is not available by default. See plans and pricing.
🤔 API or Zapier?
They solve different problems:
Zapier connects Podyx to tools that already exist — Slack, a CRM, a spreadsheet, your email platform — with no code. See Zapier & API Integrations.
The API is for building something of your own: a booking flow inside your own website or app, a price calculator, or an internal system that needs to read and act on your schedule.
💡 If nobody on your side writes and maintains code, Zapier is the right door. The API assumes a developer is building the integration and will look after it.
🔑 Getting access
Ask us to switch it on. Get in touch through chat and we will enable the API for your studio.
Create a key in
Settings → Booking → API keys.Copy the key straight away. It is shown once, when you create it, and cannot be retrieved afterwards. If you lose it, create a new one.
Hand it to your developer through a secure channel, with a link to the developer guides.
⚠️ An API key is a studio-wide secret. It belongs on your developer's server only — never in website code, a mobile app, a link or anything a client's browser can see. Anyone holding it can act on your studio within its permissions.
If a key leaks or you stop working with a developer, revoke it in Settings → Booking → API keys. A revoked key stops working at once; keys you have not revoked carry on.
🔒 What a key is allowed to do
A key acts with the permissions of the team member who created it, checked on every call — reads as well as writes. If that person's role does not allow something in the CMS, the key cannot do it through the API either.
Some actions need several permissions at once. Taking a booking, for example, needs permission to create sessions, read clients and collect payments; if the role is missing any one of them, the booking is refused.
⚠️ Changing that person's role, or removing them from your team, changes what the integration can do — immediately. This is the most common reason an integration that worked yesterday is refused today.
💡 Create keys from a dedicated team account with a role built for the integration, with exactly the permissions it needs. Then a staff change never breaks it by accident. Roles are set up in Settings → Team → Roles — see Roles & Permissions.
🧰 What you can build with it
The API covers the whole client journey, from browsing to after the session:
Your catalog — the services, rooms, setups and add-ons clients can buy, with images, capacity and how they fit together.
Availability — free time per room, and the exact start times a client can pick for a given service, setup and length, in your studio's time zone.
Price quotes — the real price Podyx would charge, including pricing rules, day rates, tax, promo codes and the client's credits, plus anything still needed before booking (form answers, guests, terms to accept).
Clients — find or add clients to your studio.
Bookings — create bookings with one or more sessions, including studio tours.
After booking — reschedule, change what was booked, manage guests, sell add-ons and cancel, whole bookings or single sessions.
Payments — take payment through your connected Stripe or Square account or as cash, or record money your studio collected some other way.
Bundles and subscriptions — let clients book with sessions they already own, and read purchased bundles with their usage and validity.
📏 Your studio's rules still apply
A booking made through the API goes through the same checks as one made on your booking page:
Prices are always calculated by Podyx. An integration cannot set its own price; promo codes and credits are applied by Podyx's rules too.
Your booking rules, capacity and required details — booking form questions, guest limits, terms acceptance — are enforced. A booking missing something your studio requires is refused.
A session cannot be booked onto a time that has already passed, and a bundle or subscription session cannot run past midnight.
⚠️ Showing availability or a price does not hold the slot. Nothing is reserved until the booking is made, and Podyx rechecks everything at that moment. If someone else took the time in between, the booking is refused and the client picks again.
👀 What your team should know once it is live
Clients added through the API cannot sign in to Podyx yet. They exist on your studio and can be booked, but creating a client or a booking does not send them an invitation. Your integration can request an activation invitation when you want a client to have a Podyx login.
A booking that came in is not necessarily paid or approved. Payment, your approval and the session itself are tracked separately — check the session in Sessions as you would any other.
Money you collect outside Podyx is reported, not taken. If your integration takes payment its own way, it tells Podyx what was collected. Refunds of that money are made by you, outside Podyx, and then recorded — cancelling a session does not move money on its own.
Retries do not double-book. An integration built to the developer guides can safely retry after a timeout without creating a second booking or a second charge.
🔁 If you already have an integration
The current API is version 2. The earlier version stays available, so existing integrations keep working. New integrations should be built on version 2, which covers complete booking flows end to end.
📚 For your developer
Developer guides — start here: access, catalog, availability, quotes, clients, bookings, payments, and safe retries.
Full API reference — every endpoint, field, permission and error, including catalog administration, bundles and subscriptions.
OpenAPI specification — for code generators and API tools.
✅ Summary
The Podyx API is for building your own booking flow or internal tools on top of Podyx; if you just want Podyx talking to tools you already use, Zapier is simpler. It is a Premium feature switched on per studio on request — ask us, then create a key in Settings → Booking → API keys, copy it the moment it is shown, and keep it on your developer's server only. A key can do exactly what its creator's role allows, so create keys from a dedicated account with a role built for the integration. Through the API you can read your catalog and availability, get real price quotes, add clients, take and manage bookings, and handle payment — always within your studio's rules and prices. Showing availability does not hold a slot, clients added through the API cannot sign in until you request an invitation, and a booking that arrives may still need payment or your approval. Point your developer to the developer guides to get started.
Related: Zapier & API Integrations · Roles & Permissions · Sessions · Connect Your Payments · Booking Rules