When developers first look at Orita, they often ask: "Is this just for coaches and therapists?"
No. It's for any business that sells time.
The same POST /api/v1/bookings call that books a therapy session works identically for a legal consultation, a property tour, a medical appointment, or a salon visit. The infrastructure is vertical-agnostic. What changes is the context your AI agent brings to the call — not the API itself.
Here's how that works in practice, and why it matters if you're building AI scheduling agents.
The Problem Every Scheduling API Has
Most scheduling tools were built for one type of business. Calendly was built for sales calls. Acuity was built for coaches. Mindbody was built for gyms.
When you try to use these tools as backend infrastructure — especially across multiple providers in different service categories — you hit walls fast:
- Single-owner APIs: Acuity's entire API is scoped to one business. No multi-provider support.
- Consumer-first design: Calendly has no programmatic booking for third-party AI agents.
- Vertical lock-in: Mindbody works for fitness. Square Appointments works for beauty. Neither works for both.
Orita's API was designed differently. The model is simple:
- A provider (doctor, lawyer, agent, tutor, stylist) registers and sets their availability
- A platform (your app) connects to multiple providers via a single API key
- An AI agent calls the API to discover, check availability, and book — in any context
The vertical doesn't change the API contract. It changes what your agent does with the data.
Same API, Different Verticals
Here's the same core booking call adapted to four different industries:
Healthcare
POST /api/v1/bookings
Authorization: Bearer orita_your_key
{
"eventTypeId": "evt_initial-consultation",
"providerId": "dr-garcia",
"date": "2026-08-15",
"time": "10:00",
"clientName": "Maria",
"clientLastname": "Lopez",
"clientEmail": "maria@example.com",
"notes": "First visit — reporting anxiety symptoms"
}
Your AI agent replaces the call center. It checks GET /api/v1/slots in real time, picks the first available slot that matches the patient's preference (morning, near their location), and books it instantly. Confirmations go out via webhook. No human in the loop.
→ Scheduling API for Healthcare
Legal
POST /api/v1/bookings
Authorization: Bearer orita_your_key
{
"eventTypeId": "evt_free-consultation",
"providerId": "atty-rodriguez",
"date": "2026-08-16",
"time": "14:00",
"clientName": "James",
"clientLastname": "Chen",
"clientEmail": "james@example.com",
"notes": "Employment dispute — needs urgent review"
}
A lead lands on a law firm's site, describes their situation to a chatbot, and the agent books the consultation in the same conversation. No email tag. No waiting 24 hours for a call back. Lead converted in under 60 seconds.
Real Estate
POST /api/v1/bookings
Authorization: Bearer orita_your_key
{
"eventTypeId": "evt_property-tour",
"providerId": "agent-kim",
"date": "2026-08-17",
"time": "11:00",
"clientName": "Sofia",
"clientLastname": "Park",
"clientEmail": "sofia@example.com",
"notes": "Interested in 3BR properties, budget €350k"
}
A buyer fills out a property search form, an AI agent picks the three most relevant listings, checks the agents' availability via GET /api/v1/slots, and books tours for all three — sequentially, same day. The buyer gets a confirmation email for each. The agent gets a webhook event to prepare.
→ Scheduling API for Real Estate
Beauty & Wellness
POST /api/v1/bookings
Authorization: Bearer orita_your_key
{
"eventTypeId": "evt_haircut-color",
"providerId": "stylist-ana",
"date": "2026-08-18",
"time": "13:00",
"clientName": "Laura",
"clientLastname": "Gomez",
"clientEmail": "laura@example.com"
}
A voice agent embedded in a salon's WhatsApp number takes bookings 24/7. The salon has three stylists, each with their own provider account. Each service (haircut, color, blowout) is a separate event type with a different duration. Buffer time between appointments is set per event type. No double-booking. No manual coordination.
→ Scheduling API for Beauty & Wellness
What Makes This Work Across Verticals
The reason Orita's API generalizes is its data model. Every booking is:
- Provider — any person or business that offers time slots
- Event type — a service with a name, duration, price, and availability schedule
- Slot — a specific available window
- Booking — a confirmed reservation linking a slot to a client
That's it. A therapy session, a legal consultation, a property tour, and a haircut are all just bookings. The labels change. The infrastructure doesn't.
Multi-provider by default
Unlike single-owner APIs, Orita's platform model lets you manage hundreds of independent providers under one API key:
# Create a provider linked to your platform
POST /api/v1/professionals
{
"names": "Ana",
"lastnames": "Torres",
"email": "ana@salon.com",
"country": "España"
}
# Returns: professionalId, their own API key, profile URL
Your agent can then route bookings to the right provider based on specialty, location, availability, or any logic you implement.
Webhooks close the loop
Every booking event — created, confirmed, cancelled, rescheduled — fires a webhook to your endpoint:
{
"event": "booking.created",
"data": {
"bookingId": "bkg_abc123",
"providerId": "dr-garcia",
"clientEmail": "maria@example.com",
"startTime": "2026-08-15T10:00:00Z",
"eventType": "initial-consultation"
}
}
Use this to trigger confirmation emails, update your CRM, notify the provider via Slack, or start any downstream workflow. Works identically across all verticals.
Vertical-Specific Features (Already Built)
Some industries need more than just basic booking. Several field-level features in Orita's event type model address common vertical requirements without custom code:
| Feature | Use case |
|---|---|
| bufferTime | Automotive: 15-min cleanup between service appointments |
| schedulingNoticeDays | Legal: require 48h advance booking for consultations |
| medicalInsuranceAllowed | Healthcare: collect insurance card on booking |
| identityDocumentAllowed | Financial: KYC document upload at booking time |
| telephoneAllowed | Home Services: collect phone for day-of coordination |
| meetingLink | Education: auto-attach Zoom link for online tutoring |
These aren't add-ons. They're parameters on the event type object, configurable via API or the provider's dashboard.
Building a Multi-Vertical AI Scheduling Platform
If you're building a platform that serves multiple service categories — think Zocdoc for any industry, or an AI concierge that books across verticals — the platform API flow looks like this:
1. POST /api/v1/professionals → onboard providers per vertical
2. Configure event types → services with duration, price, availability
3. GET /api/v1/professionals → list & filter your network
4. GET /api/v1/slots → check availability in real time
5. POST /api/v1/bookings → create the booking
6. Webhook → handle confirmation downstream
Your AI agent handles steps 3–5 at runtime. Steps 1–2 are onboarding, done once per provider.
The same loop works for a healthcare platform managing 50 doctors, a legal marketplace with 200 attorneys, or a beauty booking network with 1,000 salons.
Getting Started
The fastest way to test multi-vertical booking:
# 1. Get your API key
curl https://orita.online/sign-up?lang=en
# 2. Create your first booking (single professional)
curl -X POST https://orita.online/api/v1/bookings \
-H "Authorization: Bearer orita_your_key" \
-H "Content-Type: application/json" \
-d '{
"eventTypeId": "evt_your_event",
"date": "2026-08-01",
"time": "10:00",
"clientName": "Test",
"clientLastname": "User",
"clientEmail": "test@example.com"
}'
The free tier covers your first 50 bookings. No credit card required.
For vertical-specific docs, use cases, and code examples:
- Healthcare scheduling API
- Legal scheduling API
- Real estate booking API
- Financial services scheduling API
- Beauty & wellness booking API
- Education scheduling API
- Home services booking API
Or start with the full API reference.