200 | OK. The request succeeded. |
201 | Created. A new record (contact, company, email, custom field, activity) was created. |
204 | No Content. The request succeeded and there is nothing to return, for example a delete. |
400 | Bad Request. The payload or query parameters failed validation. Check the response body for which field is invalid. |
401 | Unauthorized. The API key is valid, but the record you asked for doesn’t belong to that key’s client (or agency, for master keys). |
403 | Forbidden. The request is missing the X-API-KEY header, or the key doesn’t match any record. See Authentication. |
404 | Not Found. No record exists with the ID you supplied. |
409 | Conflict. You tried to create a contact or company that already exists for this client, matched by email, LinkedIn URL, or phone. The response includes the existing record’s id. |
422 | Unprocessable Entity. Custom field values failed validation, for example a field name that isn’t defined in your schema, or a value that doesn’t match the field’s type. |
429 | Too Many Requests. This API key went over its rate limit of 90 requests per 10 seconds. The request was not processed; wait and retry. |
500 | Internal Server Error. Something failed on RevyOps’s side. Retry later; contact support if it persists. |