A buyer fills out a property inquiry form. Your team identifies the right agent, checks their calendar, sends an email with availability options, and waits. By the time you confirm, the buyer has already toured with another listing. In real estate, 30-minute response time is the difference between a deal and a lost lead.
A real estate platform with 50 agents and 200 listings has no scalable way to route a tour request to the right agent's calendar. Spreadsheets, shared calendars, and Calendly links per agent don't compose into a reliable platform feature.
When availability is checked manually — or via a slow sync with Google Calendar — you get race conditions. Two buyers request the same slot. One gets confirmed and the other gets a manual apology email. A real-time availability API eliminates this entirely.
Orita's availability endpoint returns open slots in real time. Your AI agent or listing page shows buyers exactly when they can tour — and creates a confirmed booking the moment they pick a time. No manual coordination, no back-and-forth.
Pass `provider_username` to book with any agent — by property, location, language, or specialty. Your matching logic lives in your platform; Orita handles the scheduling. One API key manages your entire agent roster.
Register your CRM or listing platform as a webhook endpoint. Confirmed tours, cancellations, and reschedules all trigger an immediate POST. Update lead status, notify the agent, and log the interaction — automatically, every time.
Your AI agent identifies the right listing agent and creates the viewing booking instantly.
{
"provider_username": "agent-martinez",
"event_type_id": "property-tour",
"lead_name": "David Chen",
"lead_email": "david@example.com",
"start_time": "2026-04-05T11:00:00Z",
"notes": "Interested in 3-bed unit, needs parking. Listing #MX-4421"
}Response includes booking_id, confirmation_url, and agent contact details.
Yes. Each agent is a provider in your Orita account. Your platform decides which agent to book based on property assignment, location, or availability — and passes the right provider_username when creating the booking.
PATCH /bookings/:id lets you update the booking time. The webhook fires again with the new details so your agent, calendar, and CRM all stay in sync. No manual updates required.
Yes. Configure buffer time on the event type in Orita. When an agent finishes one tour, the buffer time is automatically blocked before the next booking can be created — preventing back-to-back tours with no travel time.
Yes. Create different event types for open houses and private tours. Open houses can have group capacity settings; private tours are one-on-one. Your AI agent or listing page picks the right event type when creating the booking.