Developers
The Reeve API — call Reeve's CRM, Memory, and Comms products over HTTPS with a single API key. Plus webhooks, the SDK & embeds, and how to build an app.
Developers
Reeve is a hosted AI marketing and operations platform for ecommerce brands. The Reeve API lets you build on top of that platform — read and write the customer graph, run enrichment, and drive conversations — over plain HTTPS with a single API key.
Everything below is for the hosted product. You don't run any Reeve infrastructure: you authenticate with an API key and call https://api.meetreeve.com.
Base URL
https://api.meetreeve.comAll endpoints are versioned and namespaced by product, e.g. /api/crm/v1/contacts.
Authentication in brief
Authenticate every request with a Reeve API key sent as a Bearer token:
curl https://api.meetreeve.com/api/crm/v1/contacts \
-H "Authorization: Bearer rcm_your_api_key"API keys are created in the Reeve app, shown once, and revocable. See Authentication & API keys for the full model.
Public products
The API surfaces three products today. Each has its own versioned namespace and is documented in the API reference.
| Product | Namespace | What it covers |
|---|---|---|
| CRM | /api/crm/v1 | Contacts, audiences, interactions, enrichment, suggestions — the Reeve customer graph |
| Memory | /api/enrich/v1 | Enrichment jobs, artifacts, and suggestions that derive and propose structured facts |
| Comms | /api/comms/v1 | Conversational tool-call surface for messaging and delivery events |
Public vs internal namespaces. Only CRM, Memory, and Comms are public, documented, API-key-authenticated surfaces. Everything else in the Reeve backend (billing, connector management, Studio/AdBuyer internals, and service-to-service routes that authenticate with an internal X-Reeve-Service-Token) is internal and not part of the public API. The Voice product is planned and will become public when its spec lands.
Reference is generated from OpenAPI
The API reference is generated from truth-derived OpenAPI specifications — the same schemas the live API is built from — so it stays in sync with what the service actually does. The specs are committed under openapi/ and guarded by a drift check.
Explore
Authentication & API keys
Create, send, and revoke API keys. The Bearer-token model and request headers.
API reference
Every endpoint across CRM, Memory, and Comms, generated from OpenAPI.
HTTP or MCP
Same generated catalog, two transports — when to call REST directly vs. connect an agent over MCP.
Webhooks & events
Receive signed event callbacks when things happen in Reeve.
SDK & embeds
The in-app SDK for apps that run inside Reeve.
Build an app
Ship an app that lives inside the Reeve app, and get it reviewed.