Public API v2
Public API v2 is being documented as a new API surface. Confirm that your workspace has access before building production integrations against it.
Reevo Public API v2 is designed for integrations that need to create, update, query, and connect CRM records using a consistent object model.
Use it when you need to:
- Sync contacts, accounts, and opportunities from another system into Reevo
- Build a custom workflow that reads CRM state and writes back updates
- Query records with filters, sorting, and cursor pagination
- Attach relationships between records, such as contacts on accounts or contacts on opportunities
- Work with custom objects through the same record and relationship patterns as standard objects
OpenAPI specification
The generated OpenAPI spec for this section is checked into the knowledge base at:
/api-reference/public-api-v2/openapi.json
Mintlify uses that file to generate the endpoint reference pages in this section.
Use the curated guides when you want to understand a workflow. Use the API reference when you need exact request and response schemas.
Base URL
https://api.reevo.ai/api/v2
Authentication
Send your Reevo API key on every request. Prefer the bearer token form:
curl "https://api.reevo.ai/api/v2/contact/<contact_id>" \
-H "Authorization: Bearer <your-api-key>"
X-Api-Key: <your-api-key> is also accepted for compatibility.
API keys are created in Reevo under Settings -> Integrations -> API keys. Use the narrowest permissions that match your integration.
Response shape
Single-record responses return a data object:
{
"data": {
"id": "9b4f2fb1-2a7f-4d75-8d5f-3f3f0d7f2a7a",
"record_type": "contact",
"attributes": {
"first_name": {
"value_type": "string",
"value": "Sarah"
},
"primary_email": {
"value_type": "email",
"value": "sarah.chen@acme.com"
}
}
}
}
List and query responses return data plus pagination metadata.
Core resources
The initial v2 surface includes these standard resources:
| Resource | Use it for |
|---|
contact | People in your CRM, including names, emails, phones, owners, stages, and account/opportunity relationships |
account | Companies and organizations, including domains, owners, stages, and related contacts |
opportunity | Deals or pipeline records, including stages, amounts, accounts, and contact roles |
task | Action items assigned to users or associated with CRM records |
note | Notes attached to CRM records |
meeting | Read-only meeting records, media, transcripts, and related records |
activity | Activity timeline reads and manual activity creation |
| Custom objects | Workspace-defined objects addressed by their object API name |
Start with Core Objects for the record model, value envelopes, writes, filters, and relationships.
Recommended path
- Start with Quickstart to make your first request.
- Check Supported Resources before assuming a record type supports every action.
- Use workflow guides for common integration jobs:
- Use object guides for resource-specific behavior:
- Use Not Supported Yet to avoid design-note examples that are not live in Public API v2.