Horato documentation

Use the REST API for server-side product integrations. Use the dashboard panel to operate organizations, applications, API keys, account connections, billing, and webhook health. Use MCP when an agent needs read tools and approval-gated write tools over the same action model.

• REST API: normalized resources, external IDs, etags, raw payloads, sync cursors, and signed webhooks.
• Panel: operational UI for setup, monitoring, billing, keys, and repair workflows.
• MCP: resource-safe tools for search, availability, booking, task, and email workflows.

Production API traffic uses `https://api.hora.to`. Public docs live at `https://hora.to/docs`.

curl https://api.hora.to/v1/email/messages \
  -H "Authorization: Bearer $HORATO_API_KEY" \
  -H "Content-Type: application/json"

One API key unlocks every product domain. Each domain has its own guide; the API reference lists every endpoint.

• Email: read, search, send, provider-native drafts, dynamic templates, scheduled send, and AI summarize/classify/extract/clean over Gmail, Microsoft 365, and custom IMAP/SMTP.
• Calendar: calendars, events, free/busy, RSVP, and a Horato-native virtual calendar for accounts with no Google/Microsoft/Apple calendar.
• Scheduling: white-label event types, availability, bookings, reschedule/cancel, and opt-in confirmation + reminder emails.
• AI meeting notetaker: start a bot, fetch the post-call transcript and recording, and receive signed lifecycle events.
• Contacts and tasks: normalized read/write across connected providers.
• Webhooks and MCP: signed realtime events and approval-safe agent tools over the same action model.

OpenAPI, Postman, and LLM text exports are generated from the same docs registry and spec-derived endpoint catalog.

• `/docs/openapi.json` for schema-aware tools.
• `/docs/postman.json` for manual API exploration.
• `/llms.txt` for short agent discovery.
• `/docs/llms-full.txt` for a complete plain-text docs snapshot.