Overview
RevyOps gives you more than one way to find a record. This page lists, per object, which identifiers the public API accepts and which endpoint to use for each.Contacts
A contact’s email, LinkedIn URL, and phone are each optional, but a contact needs at least one of them to be created. See Create Contact.
Companies
A company’s domain is its primary identifier: it’s required to create a company, and it’s what RevyOps uses to auto-associate a contact with a company from the contact’s email address.
People
GET /public/people/lookup requires exactly one identifier. Use GET /public/people instead when you want to search across several fields at once, or don’t have an exact identifier value.
Emails
Looking Up by Custom Field
Contacts and companies can also be found by the value of a custom field you’ve defined, using:GET /public/contacts/lookup-by-custom-field?field_name=...&field_value=...GET /public/companies/lookup-by-custom-field?field_name=...&field_value=...
field_name and field_value and return up to 100 matching records. This is useful when a custom field (an external CRM ID, for example) is the identifier you actually have on hand, rather than an email or domain. See Custom Fields for how fields are defined.
company_id Shortcut on Writes
When creating or updating a contact, thecompany_id field accepts either an integer company ID or a domain string. Passing a domain auto-resolves it to the matching company, so you don’t have to look up the company ID yourself first.
