Create Deal

Use the Create Deal endpoint to create new deals for an Apollo account. Deals enable you to track account activity, including monetary values of a deal, deal owners, and deal stages.

To update existing deals in your Apollo account, use the Update Deal endpoint instead.

This endpoint also requires a master API key. If you attempt to call the endpoint without a master key, you will receive a 403 response. Refer to Create API Keys to learn how to create a master API key.

Body Params
string
required

Name the deal you are creating. This should be a human-readable name.

Example: Massive Q3 Deal

string

The ID for the deal owner within your team's Apollo account.

Use the Get a List of Users endpoint to retrieve IDs for all of the users within your Apollo account.

Example: 66302798d03b9601c7934ebf

string

The ID for the account within your Apollo instance. This is the company that you are targeting as part of the deal being created.

Each company in the Apollo database is assigned a unique ID. To find IDs, call the Organization Search endpoint and identify the values for organization_id.

Example: 5e66b6381e05b4008c8331b8

string

The monetary value of the deal being created.

Do not enter commas or currency symbols for the value. The currency is automatically populated by the settings within your Apollo account. Commas are not accepted and result in the deal amount being left blank.

Example: 55123478 (results in a deal value of $55,123,478 if the default currency is USD)

string

The ID for the deal stage within your team's Apollo account.

Each deal stage is assigned a unique ID. To find deal stage IDs, call the List Deal Stages endpoint and identify the value for id for each stage.

Example: 6095a710bd01d100a506d4bd

date

The estimated close date for the deal. This can be a future or past date.

The date should be formatted as YYYY-MM-DD.

Example: 2025-10-30

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

Language
Credentials
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
text/plain