Most tutoring businesses — from independent tutors to mid-size academies — coordinate sessions via WhatsApp, email, or a shared Google Sheet. When a student wants to book a session, someone manually checks the tutor's availability and confirms a time. It's slow, error-prone, and doesn't scale.
An online tutoring platform serving students in Spain, Mexico, and the US deals with booking requests across 4+ timezones. Manual scheduling means someone is always sending 'that's 3 AM for me' replies. Without timezone-aware availability, you lose students to friction.
A student requests an Advanced Python tutor available Tuesday mornings. Your platform knows which tutors teach Python. But routing that request to the right tutor's calendar — by subject, level, language, and availability — requires infrastructure you haven't built yet.
Orita's availability API returns open slots in the requested timezone. A student in Tokyo sees available times in JST; a student in Madrid sees them in CET. The underlying booking is stored in UTC. No timezone confusion, no scheduling errors.
Your platform logic determines which tutor to route to — by subject, proficiency level, spoken language, or availability. Pass `provider_username` and Orita creates the booking on the right tutor's calendar. One API key for your entire tutor network.
Your AI onboarding or study assistant can ask about subject, preferred time, and language — then call Orita's API to find a matching tutor and book the first session without leaving the conversation. The student goes from inquiry to confirmed booking in under 60 seconds.
Your chatbot matches student to tutor, then creates the session. Timezone conversion is handled automatically by Orita.
{
"provider_username": "tutor-nakamura",
"event_type_id": "python-session-60min",
"student_name": "Lucas Ferreira",
"student_email": "lucas@example.com",
"start_time": "2026-07-08T18:00:00Z",
"notes": "Level: intermediate. Goal: async/await and FastAPI basics"
}Response includes booking_id, meet_url (if integrated), and tutor timezone details.
Yes. Each provider (tutor) sets their availability in their local timezone. When your platform or AI agent calls the availability endpoint, you specify the student's timezone and receive slots already converted. Bookings are stored in UTC to avoid ambiguity.
Routing logic lives in your platform. You maintain the subject/language mapping for each tutor. When a student requests a session, your code selects the matching tutor_username and passes it to the Orita API. Orita handles the availability check and booking creation.
Create a separate booking for each session. Your platform can automate this by looping through weekly dates and calling the Orita bookings API for each one. The student and tutor receive confirmation for every session, with reminders firing 24h before each.
Yes. Orita ships official JavaScript/TypeScript and Python SDKs. Most education AI stacks are built on one of these — the SDK gives you typed responses, auto-retry logic, and availability helpers without writing raw HTTP calls.