/v1/contacts/save-developersSave developers as contacts
contact:createBulk save 1..500 developers as contacts, each with its own source reason and do-not-contact bit. Backs the onboarding moment: a company's own top devs save do-not-contact (own-company), competitor devs save contactable (competitor). Idempotent: re-adds restore removed contacts, and each saved row is converged to its requested do-not-contact state.
Request body SaveDevelopersRequest
developersarray of object requiredThe developers to save, 1 to 500 at a time, each with its own do-not-contact bit.
min 1 items, max 500 itemsdeveloperIdstring requiredThe developer to save.
max 200 charsdoNotContactboolean requiredTrue to save them as do-not-contact, which is how you record your own employees so outreach can never reach them. False to save them as contactable.
sourcestringWhy they are being saved, recorded as provenance. Defaults to a manual add.
searchfeedimportmanualapilookupown-companycompetitorsourceDetailstringFree-text detail behind `source`.
max 1000 chars
Responses
200Save resultcreatedarray of string requiredContacts newly created by this call.
restoredarray of string requiredContacts that had been removed and were brought back, rather than created fresh. Their history is intact.
existingarray of string requiredContacts that were already present and were left as they were.
400Empty, too many, or non-numeric idscodestring requiredStable machine-readable error code. Branch on this, never on the numeric status.
bad_requestunauthorizedsignature_requiredpayment_requiredforbiddennot_foundconflictgonepayload_too_largeunprocessable_entitytoo_many_requestsinternal_errornot_implementedbilling_unavailablenot_contactablemailbox_link_unavailablemailbox_requiredmail_engine_unavailablewebhook_publisher_unavailabledatabase_unavailableclient_errormessagestring requiredHuman-readable explanation of the refusal.
statusinteger requiredThe HTTP status code, repeated in the body.
remedyobjectA self-serve path forward, when one exists (a 402 points at the credit top-up).
kindstring requiredWhat kind of remedy this is, so a client can route it: whether the caller can clear the condition through the API, or a person must act in the web app.
topupconnect_mailboxurlstring requiredWhere to go to clear the condition: an API path, or a web app page when only a person can.
401No or invalid credentialcodestring requiredStable machine-readable error code. Branch on this, never on the numeric status.
bad_requestunauthorizedsignature_requiredpayment_requiredforbiddennot_foundconflictgonepayload_too_largeunprocessable_entitytoo_many_requestsinternal_errornot_implementedbilling_unavailablenot_contactablemailbox_link_unavailablemailbox_requiredmail_engine_unavailablewebhook_publisher_unavailabledatabase_unavailableclient_errormessagestring requiredHuman-readable explanation of the refusal.
statusinteger requiredThe HTTP status code, repeated in the body.
remedyobjectA self-serve path forward, when one exists (a 402 points at the credit top-up).
kindstring requiredWhat kind of remedy this is, so a client can route it: whether the caller can clear the condition through the API, or a person must act in the web app.
topupconnect_mailboxurlstring requiredWhere to go to clear the condition: an API path, or a web app page when only a person can.
403Missing contact:createcodestring requiredStable machine-readable error code. Branch on this, never on the numeric status.
bad_requestunauthorizedsignature_requiredpayment_requiredforbiddennot_foundconflictgonepayload_too_largeunprocessable_entitytoo_many_requestsinternal_errornot_implementedbilling_unavailablenot_contactablemailbox_link_unavailablemailbox_requiredmail_engine_unavailablewebhook_publisher_unavailabledatabase_unavailableclient_errormessagestring requiredHuman-readable explanation of the refusal.
statusinteger requiredThe HTTP status code, repeated in the body.
remedyobjectA self-serve path forward, when one exists (a 402 points at the credit top-up).
kindstring requiredWhat kind of remedy this is, so a client can route it: whether the caller can clear the condition through the API, or a person must act in the web app.
topupconnect_mailboxurlstring requiredWhere to go to clear the condition: an API path, or a web app page when only a person can.