API Reference
The Reeve product API — CRM, Memory, Comms, Channels, Enrich, and Voice over HTTP.
The Reeve API lets your app consume individual Reeve products à la carte over HTTP. This reference is generated directly from the live API and is verified against it on every deploy, so it never drifts from what the server actually does.
Base URL
https://api.meetreeve.comProducts
| Product | Base path | What it does |
|---|---|---|
| CRM | /api/crm/v1 | Contacts, lifecycle, audiences |
| Memory | /api/memory/v1 | Namespaced hybrid (vector + lexical) memory + knowledge graph |
| Comms | /v1/comms | Transactional email & SMS |
| Channels | /api/channels/v1 | Slack and other channel messaging |
| Enrich | /api/enrich/v1 | Recipe-driven enrichment |
| Voice | /api/voice/v1 | Voice agents, calls, and agent tools |
Authentication
Every request authenticates with a host-app key in the X-Reeve-Host-Key header, plus your X-Reeve-Host-App identifier. See Authentication.
Machine-readable spec
The full, filtered OpenAPI spec is published for tools and LLMs:
https://api.meetreeve.com/openapi/public/v1.jsonPer-product specs are at https://api.meetreeve.com/openapi/public/{product}-v1.json (e.g. crm-v1.json). Drop either into your LLM to explore the whole API.
Every page in this reference is also available as plain markdown — request it with
Accept: text/markdown, or see llms.txt / llms-full.txt.