OnSched APIs for AI Agents
ProductivityCalendar SchedulingMonitoring ObservabilityOfficial Vendor SpecsOAuth 2.0Agent Ready
OnSched API Catalog
3 APIs across 2 product groups. All share one credential.
Productivity2
OnSched Setup APIConfigure companies, services, resources, calendars, and business rules that back OnSched booking flows using OAuth 2.0 client-credentials authentication.~139 endpointsOnSched Consumer APISearch availability, create and book appointments, and manage customer records for online booking flows using OAuth 2.0 client-credentials authentication.~38 endpoints
Which OnSched API should I use?
| I want to... | Use | Why |
|---|---|---|
| Configure companies, calendars, services, resources, and business users | OnSched Setup API | The Setup API owns tenant provisioning and admin-side calendar, block, and appointment-reassignment operations across 139 endpoints. |
| Search availability and book, reschedule, or cancel appointments for end users | OnSched Consumer API | The Consumer API is the booking surface that operates on an already-configured profile, with availability search and appointment lifecycle actions. |
| Confirm the OnSched platform is reachable before issuing booking or provisioning calls | OnSched API Utility | The Utility API exposes heartbeat and thread-info health checks and is the lightest call to gate a workflow on. |
Install Jentic One Beta
Connect the OnSched APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OnSched APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring OnSched by hand means running the OAuth 2.0 client-credentials flow, tracking token expiry, and calling three separate surfaces for setup, booking, and health. With Jentic you install Jentic One once, add the OnSched APIs you need from the Jentic directory, store the client credentials once, and your agent calls them.
Permission scoping
OnSched puts calendar and appointment ids in the URL path, so your own rules can pin the agent to specific operations and resources. You decide whether it can only read health and availability, or also provision companies and book, so account-shaping calls are not available unless you add them.
Credential isolation
Your OnSched client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context, and the same credential covers all three OnSched APIs.
FAQs
Specific to using OnSched APIs through Jentic.
What can an agent do across the OnSched APIs?
An agent can run the whole booking lifecycle. It can provision a tenant with the Setup API by creating companies, calendars, services, resources, and business users, then take live bookings with the Consumer API by searching availability and creating, booking, rescheduling, or cancelling appointments, and it can gate that work on a platform health check from the Utility API.
Do the three OnSched APIs share one credential?
Yes. Setup, Consumer, and Utility all use the same OAuth 2.0 client-credentials scheme, with a ClientId and Secret bound to a company profile. One credential set authenticates against all three, so an agent does not manage separate secrets per API.
Which OnSched API should I start with?
Start with the Setup API if you need to configure a booking backend, since companies, calendars, services, and resources must exist before bookings can be made. Use the Consumer API once a profile is configured and you want to search availability and book for end users. Use the Utility API for health checks and readiness gates.
How do the OnSched APIs fit together in one workflow?
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
