Create a Contact
Creates a new contact in Apollo.
Query
Comma-separated response fields to include.
Body
The first name of the contact you want to create. Example: `Tim`
The last name of the contact you want to create. Example: `Zheng`
The name of the contact's employer (company). Example: `apollo`
The current job title that the contact holds. Example: `senior research analyst`
The Apollo ID for the account. Example: `63f53afe4ceeca00016bdd2f`
The email address of the contact. Example: `[email protected]`
The corporate website URL. Example: `https://www.apollo.io/`
Lists to which the contact belongs.
The Apollo ID for the contact stage. Example: `6095a710bd01d100a506d4ae`
The personal location for the contact. Example: `Atlanta, United States`
The primary phone number. Example: `555-303-1234`
The work/office phone number. Example: `+44 7911 123456`
The mobile phone number. Example: `555-303-1234`
The home phone number. Example: `555-303-1234`
Alternative phone number. Example: `555-303-1234`
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"}`
Set to `true` to enable deduplication logic that prevents creating duplicate contacts. When enabled, Apollo will check for existing contacts with matching email addresses, names, or other identifying information and return the existing contact instead of creating a duplicate. The default value is `false`. When deduplication is enabled, performance may be slightly impacted due to the additional validation checks, but this ensures data integrity and prevents duplicate entries in your database.