Recho Developers
Developer documentation for integrating with the Recho platform. This site publishes the specifications you need to build external integrations and automations.
What is Recho
Recho is an AI voice-calling platform. It handles outbound and inbound automated calls and exposes two integration surfaces for external systems: a REST API and Webhooks.
What we publish
REST API (rolling out)
Programmatic access to placing calls, receiving calls, updating configuration, and retrieving logs. Specifications will be published here as features roll out.
Webhooks (available now)
Real-time delivery of call status changes, errors, completion events, and more to endpoints you control. Four endpoint types are supported (Slack / Microsoft Teams / Email / Custom HTTPS), with authentication, retry, and idempotency semantics suitable for production use.
Start with the Webhook Setup Guide.
Documentation map
| Page | Contents |
|---|---|
| Setup Guide | Quickstart / setup flow / delivery behavior (incl. FIFO) |
| Authentication | Choosing and implementing NONE / BEARER / RSA signature verification |
| Payload Spec | JSON structure, what each field is for, and the error-code catalog |
| callStatus Reference | Possible values of body.data.callStatus and how they map to eventType |
| Events | When each of the 18 eventType values fires |
| Sample Receivers | Reference implementations in Node.js / Python / Slack / Teams / Email |
| Retry Policy | Failure-retry schedule and idempotency guidance |
About this documentation
The Webhook event specifications are auto-generated from the TypeScript / Valibot schemas running in Recho's backend. CI detects drift between code and the published spec on every change, so the documentation cannot fall out of sync with the implementation.
For bug reports, feature requests, or questions, please contact your Recho representative.