Create a Task

post

https://api.apollo.io/api/v1/tasks

Use the Create a Task endpoint to create a single task in Apollo for you and your team. Tasks help track the upcoming actions you need to take, such as emailing or calling a contact.

This endpoint returns the created task object.

Apollo does not apply deduplication processes when you create a new task via the API. If your entry has the same task owner, contact, and other details as an existing task, Apollo will create a new task instead of updating the existing task.

This endpoint 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

user_id

string

required

The ID for the task owner within your team's Apollo account. This is the user that will take action on the contacts.

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

Example: 66302798d03b9601c7934ebf

contact_id

string

required

The Apollo ID for the contact that you want to be on the receiving end of the action.

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

Example: 66e34b81740c50074e3d1bd4

type

string

required

Set the task to be 1 of the following task types. This enables the task owner to know the type of action they need to take.

call: Call the contact.
outreach_manual_email: Email the contact.
linkedin_step_connect: Send a LinkedIn invitation to connect with the contact.
linkedin_step_message: Send a direct message to the contact's LinkedIn profile.
linkedin_step_view_profile: View the contact's LinkedIn profile.
linkedin_step_interact_post: Interact with the contact's recent LinkedIn posts.
action_item: Take generic action for the contact. If you use this task type, Apollo recommends using the note parameter too.

priority

string

Defaults to medium

Assign a priority to the task you are creating:

high
medium
low

status

string

required

The status of the task being created. For future-facing tasks, you should use the scheduled status.

For tasks that are already completed, you can use completed or skipped.

Example: scheduled

due_at

date-time

required

The full date and time when the task will be due.

Your entry should adhere to the ISO 8601 date-time format. Apollo uses Greenwich Mean Time (GMT) by default. If you do not account for time zone differences, you could add a task due date that falls on a different day than you intended.

The value you enter can either adhere to GMT, or you can adjust the time manually by specifying in hours and minutes how much you want to offset GMT.

Example: 2025-02-15T08:10:30Z; 2025-03-25T10:15:30+05:00

title

string

A title for the task. If omitted, Apollo will display an auto-generated title based on the task type and contact name.

Example: Follow up on demo request

note

string

Add a description for the task. This should be a human-readable message.

This parameter is not required, but it is recommended as it provides the task owner with more context on the action they need to take.

Example: This contact expressed interest in the Sequences feature specifically. Be prepared to discuss.

Headers

string

enum

Defaults to application/json

Generated from available response content types

Allowed:

Responses

200200

401401

403403

422422

429429