Zenoti API
✓ Official Vendor SpecDeveloper ToolsSource Controlbearer15 EndpointsREST
For Agents
Programmatically generate access token, revoke access token. Covers 15 operations with bearer authentication.
Use for: I need to generate access token, I want to revoke access token, Search for all centers, Find all center details
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Zenoti spa/salon management API. The API exposes 15 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Zenoti API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Zenoti API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fzenoti.com%2Fzenoti" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fzenoti.com%2Fzenoti" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Zenoti API.
Generate access token
Revoke access token
List all centers
Get center details
Create guest
Use Cases
Patterns agents use Zenoti API for, with concrete tasks.
★ Developer Tools Operations
Use the Zenoti API to perform developer tools operations programmatically. The API provides 15 endpoints covering core functionality including generate access token, revoke access token, list all centers.
Call POST /tokens to generate access token
Automated Auth Management
Automate auth operations by combining multiple Zenoti API endpoints. Agents can revoke access token and then list all centers in a single workflow.
Call DELETE /tokens/sessions/revoke to revoke access token, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Zenoti API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'generate access token', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
15 endpoints — zenoti spa/salon management api.
METHOD
PATH
DESCRIPTION
POST
/tokens
Generate access token
DELETE
/tokens/sessions/revoke
Revoke access token
GET
/centers
List all centers
GET
/centers/{center_id}
Get center details
POST
/guests
Create guest
GET
/guests
List guests
GET
/guests/{guest_id}
Get guest
PUT
/guests/{guest_id}
Update guest
POST
/tokens
Generate access token
DELETE
/tokens/sessions/revoke
Revoke access token
GET
/centers
List all centers
GET
/centers/{center_id}
Get center details
POST
/guests
Create guest
GET
/guests
List guests
GET
/guests/{guest_id}
Get guest
PUT
/guests/{guest_id}
Update guest
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Zenoti API by hand means minting its bearer token from the tokens endpoint, working through center and guest paths on api.zenoti.com/v1, and coding request handling yourself. Through Jentic you install once, import Zenoti from the API Directory, store the token once, and your agent calls it.
Permission scoping
Zenoti puts the center and guest ids in the URL path (/centers/{center_id} and /guests/{guest_id}), so a rule can pin your agent to one center or guest. You choose the operations it may call, so revoking token sessions is not included unless you add it.
Credential isolation
Your Zenoti token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list centers' or 'look up a guest', and Jentic returns the matching Zenoti operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using Zenoti API through Jentic.
What authentication does the Zenoti API use?
The Zenoti API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I generate access token with the Zenoti API?
Yes. Use the POST /tokens endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Zenoti API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I generate access token through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'generate access token'. Jentic returns the matching Zenoti API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Zenoti API have?
The Zenoti API exposes 15 endpoints covering auth, bookings, centers operations.
GET STARTED