DevelopersAPI Reference
Authentication
Authenticate API requests with a host-app key and capability scopes.
Reeve API requests authenticate with a host-app key — a server-side secret issued to your application.
Headers
| Header | Required | Value |
|---|---|---|
X-Reeve-Host-Key | yes | Your host-app key (begins with rcm_) |
X-Reeve-Host-App | yes | Your host-app identifier |
X-Org-Id | sometimes | Target organization, when your app spans multiple orgs |
curl https://api.meetreeve.com/api/crm/v1/contacts \
-H "X-Reeve-Host-Key: rcm_your_key_here" \
-H "X-Reeve-Host-App: your-app"Capabilities
Each product is a capability granted to your host-app (crm, memory, comms, channels, enrich, voice). Calling a product your app hasn't been granted returns 403. You pick which products to enable per app — pay only for what you use.
Getting a key
Host-app keys are provisioned through the Reeve developer platform. Keep keys server-side; they carry the privileges of every capability granted to the app.
Webhook endpoints (provider → Reeve) and health probes are intentionally not part of this reference — they aren't called by your app.