Skip to main content
Public API v2 is the newer version of Reevo’s REST API. It covers more of your CRM than the original API: you can read and write accounts, contacts, opportunities, tasks, notes, and custom objects, log calls, meetings, and emails as activities, read meetings with their recordings and transcripts, read email threads, and look up the fields available on every object in your workspace. The original API keeps working alongside v2. If you have an existing integration built on it, see API Integrations with Other Tools.

Before you start

  • An API key. A workspace admin creates API keys in Settings → Integrations → API keys. The same keys work for both API versions. The steps for creating, managing, and expiring a key are in the API Integrations with Other Tools article linked above.
  • The right permissions on the key. Each v2 request checks that the key has the Read or Write permission for the object it touches. A request without it is refused with an insufficient_scope error.

Base URL and reference documentation

Send every v2 request to this base URL:
The full, interactive reference for every endpoint, field, and error lives here: Load the OpenAPI specification into Postman, an API client, or a code generator to get every endpoint and request shape at once.

Authenticate your requests

Pass your API key as a bearer token in the Authorization header:
The X-Api-Key header used by the original API is also accepted, so an existing integration can switch its URLs to v2 without changing how it sends the key.
Check your setup first. GET /_me describes the key you are calling with: its user, organization, permissions, and request limits. A successful response confirms that the key is valid.

What you can do with v2

Custom objects use paths that start with cus_obj__ followed by the object’s API name, for example /cus_obj__project. Every record also exposes its custom fields by their API names.

Find the fields for each object

Field names in v2 match each object’s schema in your workspace, including your custom fields. Two endpoints describe them:
  • GET /_organization_schema_summary lists every object available in your workspace.
  • GET /_schema/{record_type} describes one object’s fields, for example GET /_schema/contact.
Check the schema before you build filters or write requests. A field that does not exist is rejected with an error that names it, rather than being silently ignored.

Read records

Read a single record by its ID:
To list records, send a POST to the object’s _query endpoint. You can filter, sort, and page through the results:
  • Filters are a list of conditions with a field, an operator, and a value. Combine conditions with and, or, and not. Operators include eq, ne, gt, gte, lt, lte, between, in, not_in, exists, not_exists, contains, starts_with, ends_with, contains_any, and contains_none.
  • Page size is set with limit, from 1 to 100. The default is 50.
  • Paging: each response includes a pagination block. To get the next page, send the same request with cursor set to the next_cursor value from the previous response. When next_cursor is null, you have reached the last page.

Create and update records

  • Create a record with a POST to the object’s path, for example POST /contact. Put the fields in an attributes object.
  • Update a record with a PATCH to its path, for example PATCH /contact/CONTACT_ID. Send only the fields you want to change.
  • Upsert a record with a POST to the object’s _upsert endpoint. Reevo looks for an existing record that matches the match field. If it finds one, it updates it and returns 200. If it does not, it creates a new record and returns 201.
This request updates the contact with the email jordan@example.com, or creates one if none exists:
Leave the matched field out of attributes. Reevo applies the matched value automatically, and it cannot be changed in the same request.

Handle errors

Every error response has the same shape, so your integration can branch on the code field:
Some errors also include a details object, for example the name of a field that does not exist. Common codes:

Request limits

Public API v2 requests count toward the same limits as the original API: a per-second speed limit and, depending on your plan, an allowance of requests for each billing period. Both apply to your whole organization. See API and MCP request limits for how the limits work and where to check your usage.

Troubleshooting / FAQs

No. The same API keys work for both versions. Make sure the key has the Read or Write permissions for the objects you want to use.
Yes. The original API keeps working, and existing integrations built on it do not need to change. Its endpoints are documented in API Integrations with Other Tools.
v2 rejects a field that does not exist on the object instead of ignoring it. Check the exact field name with GET /_schema/{record_type}, for example GET /_schema/contact.
No. Neither API version returns Reevo’s AI-generated deal, meeting, or activity summaries.

Ready to connect? Open Reevo to create your API key.