Authentication note: Shares scope with `tasks/create`.
Tasks let you track, prioritize, and help you complete actions required for your outbound sales motion.
Use the bulk create tasks endpoint to create multiple tasks in a single API request. A separate task will be created for each contact provided.
This endpoint returns a `success` boolean and a `tasks` array containing the created tasks.
Apollo doesn't 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 creates a new task instead of updating the existing task.
For creating a single task, use the create a task endpoint instead.
# OpenAPI definition
```json
{
"openapi": "3.1.0",
"info": {
"title": "apollo-rest-api",
"summary": "Programmatic access to Apollo's sales intelligence and engagement platform — data enrichment, prospect and company search, and go-to-market workflow management.",
"description": "The Apollo API provides programmatic access to [Apollo](https://www.apollo.io/), the all-in-one sales intelligence and engagement platform. Use it to enrich people and company data (individually or in bulk), search Apollo's database of over 240 million contacts and 30 million companies, and manage accounts, contacts, deals, sequences, tasks, calls, and conversations in your go-to-market workflows.\n\n## Base URL\n\nAll API requests are made to `https://api.apollo.io/api/v1`.\n\n## Authentication\n\n- **Apollo users** authenticate with an API key passed in the `x-api-key` request header. See [Create API Keys](https://docs.apollo.io/docs/create-api-key).\n- **Apollo partners** building integrations on behalf of mutual users authenticate with the [OAuth 2.0 authorization flow](https://docs.apollo.io/docs/use-oauth-20-authorization-flow-to-access-apollo-user-information-partners).\n\n## Rate limits & credits\n\nRate limits and credit consumption depend on your [Apollo pricing plan](https://docs.apollo.io/docs/api-pricing). Check your current limits and usage with the [view API usage stats and rate limits](https://docs.apollo.io/reference/view-api-usage-stats) endpoint. For more details, see [Rate Limits](https://docs.apollo.io/reference/rate-limits) and the [API FAQs](https://docs.apollo.io/docs/apollo-api-faqs).\n\nNew to the API? Start with the [Apollo API overview](https://docs.apollo.io/reference/apollo-api).",
"termsOfService": "https://www.apollo.io/terms/api",
"contact": {
"name": "Apollo API Support",
"url": "https://docs.apollo.io/"
},
"version": "1.0"
},
"servers": [
{
"url": "https://api.apollo.io/api/v1"
}
],
"tags": [
{
"name": "Tasks",
"description": "Create and search tasks for your go-to-market workflows."
}
],
"components": {
"securitySchemes": {
"apiKey": {
"type": "apiKey",
"in": "header",
"name": "x-api-key",
"description": "[Recommended] API key, passed in the `x-api-key` request header.\nSee [Create API Keys](https://docs.apollo.io/docs/create-api-key)."
},
"bearerAuth": {
"type": "http",
"scheme": "bearer",
"bearerFormat": "JWT",
"description": "OAuth 2.0 access token, used by Apollo partners building integrations.\nSee the [OAuth 2.0 authorization flow](https://docs.apollo.io/docs/use-oauth-20-authorization-flow-to-access-apollo-user-information-partners)."
}
},
"schemas": {
"ErrorDetails": {
"type": "object",
"description": "Machine-readable detail for an error that uses the new format, returned alongside the endpoint's existing error fields. The legacy error fields at the root level (`error`, `error_code`, `message`, etc) are removed on 2027-02-16, after which `error_details` is the only error payload. Some errors already return `error_details` on its own.",
"properties": {
"code": {
"type": "string",
"description": "Stable identifier in the form `DOMAIN.CATEGORY.REASON`. Branch on this value; the human-readable `message` can change.",
"example": "AUTH.AUTHENTICATION.CREDENTIALS_MISSING"
},
"message": {
"type": "string",
"description": "Human-readable explanation of what went wrong.",
"example": "This request carried no credential Apollo could authenticate."
},
"suggestions": {
"type": "array",
"description": "Ordered, actionable next steps. Each entry carries a `label`, and where relevant the `parameter`, `header`, or `url` it refers to.",
"items": {
"type": "object",
"properties": {
"label": {
"type": "string",
"example": "Send your API key in the X-Api-Key header"
},
"url": {
"type": "string",
"example": "https://docs.apollo.io/reference/authentication"
},
"parameter": {
"type": "string",
"example": "webhook_url"
},
"parameters": {
"type": "array",
"description": "Several parameters, any one of which satisfies the requirement.",
"items": {
"type": "string"
},
"example": [
"name",
"domain",
"website_url",
"linkedin_url"
]
},
"header": {
"type": "string",
"example": "X-Api-Key"
},
"example": {
"type": "string",
"description": "A valid sample value for the parameter named above."
},
"retry_after_seconds": {
"type": "integer",
"description": "On a rate-limit refusal, how long to wait before retrying.",
"example": 60
}
}
}
},
"context": {
"type": "object",
"description": "Values from your request that explain the refusal. Each entry is an object rather than a bare value, so read `context..value`. Absent when the error needs no context.",
"additionalProperties": {
"type": "object",
"properties": {
"value": {
"type": "string"
},
"description": {
"type": "string"
}
}
},
"example": {
"window": {
"value": "hourly",
"description": "The rate-limit window your request exceeded"
}
}
}
}
}
}
},
"security": [
{
"apiKey": []
},
{
"bearerAuth": []
}
],
"paths": {
"/tasks/bulk_create": {
"post": {
"summary": "Bulk create tasks",
"description": "## Endpoint essentials\n\n**API key access:** `api/v1/tasks/bulk_create` or `Master API key`\n\n**OAuth scopes:** `tasks_create`\n\n**Credit usage:** `0 credits` — [Learn more about API pricing and credits](https://docs.apollo.io/docs/api-pricing).\n\n**Authentication note:** Shares scope with `tasks/create`.\n\nTasks let you track, prioritize, and help you complete actions required for your outbound sales motion.
Use the bulk create tasks endpoint to create multiple tasks in a single API request. A separate task will be created for each contact provided.
This endpoint returns a `success` boolean and a `tasks` array containing the created tasks.
Apollo doesn't 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 creates a new task instead of updating the existing task.
For creating a single task, use the create a task endpoint instead.",
"tags": [
"Tasks"
],
"operationId": "bulk-create-tasks",
"requestBody": {
"required": true,
"content": {
"application/json": {
"schema": {
"type": "object",
"required": [
"user_id",
"contact_ids",
"type",
"status",
"due_at"
],
"properties": {
"user_id": {
"type": "string",
"description": "The ID for the task owner within your team's Apollo account. This is the user that will take action on the contacts.
Example: `66302798d03b9601c7934ebf`"
},
"contact_ids": {
"type": "array",
"items": {
"type": "string"
},
"description": "The Apollo IDs for the contacts that you want to be on the receiving end of the action.
If you add multiple contact IDs, individual tasks will be created for each of the contacts using the same task type, due date, and other details.
Example: `66e34b81740c50074e3d1bd4`"
},
"type": {
"type": "string",
"description": "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 contacts.
`outreach_manual_email`: Email the contacts.
`linkedin_step_connect`: Send a LinkedIn invitation to connect with the contacts.
`linkedin_step_message`: Send a direct message to the contacts' LinkedIn profiles.
`linkedin_step_view_profile`: View the contacts' LinkedIn profiles.
`linkedin_step_interact_post`: Interact with the contacts' recent LinkedIn posts.
`action_item`: Take generic action for the contacts. If you use this task type, Apollo recommends using the `note` parameter too.
"
},
"priority": {
"type": "string",
"description": "Assign a priority to the task you are creating:
`high`
`medium`
`low`
",
"default": "medium"
},
"status": {
"type": "string",
"description": "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": {
"type": "string",
"format": "date-time",
"description": "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`"
},
"note": {
"type": "string",
"description": "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.