Update a Contact

patch

https://api.apollo.io/api/v1/contacts/{contact_id}

Use the Update a Contact endpoint to update existing contacts in your team's Apollo account.

In Apollo terminology, a contact is a person that your team has explicitly added to your database. A contact will have their data enriched in some way, such as accessing an email address or a phone number.

To create a new contact, use the Create a Contact endpoint instead. To update the contact stage for multiple contacts, use the Update Contact Stage for Multiple Contacts endpoint.

Path Params

contact_id

string

required

The Apollo ID for the contact that you want to update.

To find contact IDs, call the Search for Contacts endpoint and identify the id value for the contact.

Example: 66e34b81740c50074e3d1bd4

Body Params

first_name

string

Update the contact's first name. Example: Tim

last_name

string

Update the contact's last name. Example: Zheng

organization_name

string

Update the employer (company) name. Example: apollo

title

string

Update the job title. Example: senior research analyst

account_id

string

Update the account ID. Example: 63f53afe4ceeca00016bdd2f

string

Update the contact email. Example: [email protected]

website_url

string

Update the employer website URL. Example: https://www.apollo.io/

label_names

array of strings

Replace lists this contact belongs to. (Passing new values will overwrite existing lists.)

label_names

contact_stage_id

string

Update the contact stage ID. Example: 6095a710bd01d100a506d4af

present_raw_address

string

Update location (city/state/country). Example: Atlanta, United States

direct_phone

string

Primary phone.

corporate_phone

string

Work/office phone.

mobile_phone

string

Mobile phone.

home_phone

string

Home phone.

other_phone

string

Alternate phone.

typed_custom_fields

object

Add information to custom fields in Apollo.

Your custom fields are unique to your team's Apollo account. This means that the examples in this documentation may not work for your testing purposes.

To utilize this parameter successfully, call the Get a List of All Custom Fields endpoint and identify the id value for the custom field, as well as the appropriate data type. For example, if a custom field accepts picklist entries, you need to pass the accompanying id value for the picklist entry that you want to use as the input value.

Example: When the Get a List of All Custom Fields endpoint returns an id of field:

"60c39ed82bd02f01154c470a" (datetime)

then the value passed should be:

{"60c39ed82bd02f01154c470a": "2025-08-07"}

Headers

string

enum

Defaults to application/json

Generated from available response content types

Allowed:

Responses

200200

401401

422422

429429