> ## Documentation Index > Fetch the complete documentation index at: https://developer.lemlist.com/llms.txt > Use this file to discover all available pages before exploring further. > Retrieves all pending tasks assigned to your team members. # Get Many Tasks export const SnippetObjectReference = ({objectName, objectPath = null}) => { const lowerCaseObjectName = objectName.toLowerCase(); if (lowerCaseObjectName === 'lead' || lowerCaseObjectName === 'leads') { return This endpoint uses the {objectName} object. Make sure to also check the {lowerCaseObjectName === 'lead' ? 'Contact' : 'Lead'} object to understand the distinction between the two. ; } return This endpoint uses the {objectName} object. ; }; This endpoint is **legacy**. Use [Search Tasks](/api-reference/endpoints/tasks/get-many-tasks-v2) instead: it exposes the filters of the Tasks page, returns completed tasks, and sorts. Tasks marked as done are automatically excluded from results. ## Filtering Use the `filters` query parameter to narrow results by: * **Lead attributes**: `fullName`, `email`, `phone`, `linkedin` (supports `value` or `regex`) * **Campaign**: `campaignId` (supports `in`/`out` arrays), `campaignState` (draft, running, ended, paused, errors, archived) * **Task properties**: `type` (manual, phone, email, linkedin, etc.), `assignedTo` (userId) * **Date range**: `dueDate` (supports `from`/`to` in YYYY-MM-DD format) Examples: ```json by date and type theme={"theme":"dracula"} [ {"filterId": "dueDate", "from": "2025-02-11", "to": "2025-02-28"}, {"filterId": "type", "in": ["phone", "linkedinSend"]} ] ``` ```json by user theme={"theme":"dracula"} [{"filterId": "assignedTo", "in": ["usr_abc123", "usr_def456"]}] ``` ## OpenAPI ````yaml get /tasks openapi: 3.0.0 info: title: lemlist API version: 1.0.0 description: >- Welcome to the lemlist Developer Documentation. lemlist is very customizable and open. You'll find on this page all the API and integration you can do with lemlist. # Rate Limit lemlist's API rate limits requests in order to prevent abuse and overload of our services. Rate limits are applied on all routes and per API key performing the request. The rate limits are **20** requests per **2** seconds. The response provides any information you may need about it: | Header | Description | | --- | --- | | Retry-After | The number of seconds in which you can retry | | X-RateLimit-Limit | The maximum requests in that time | | X-RateLimit-Remaining | The number of remaining requests you can make | | X-RateLimit-Reset | The date when the rate limit will reset | _Example of values for the rate limit headers_ ``` json { "Retry-After": 2, "X-RateLimit-Limit": 20, "X-RateLimit-Remaining": 7, "X-RateLimit-Reset" : "Tue Feb 16 2021 09:02:42 GMT+0100 (Central European Standard Time)" } ``` # Definitions ## Team A team is the entity of lemlist that can handle users and billing. ## Credits Credits are the coins a team uses to enrich emails, LinkedIn URLs, etc. via the enrich route. Each enrichment feature needs a certain amount of credits to run. ## User You use a user account to connect to lemlist and send messages via the connected emails or LinkedIn account. ## Campaign A campaign is the entity to automate outreach. A campaign has multiple sequences composed of steps. ## Lead A lead is a person that you try to contact via a campaign. ## Activity An activity is the history of all the steps. ## Unsubscribe An unsubscribe occurs when a person decides they don't want to receive emails from you anymore. # Authentication All API routes use the dedicated subdomain `api.lemlist.com`. lemlist uses API keys to allow access to the API. You can get your lemlist API key at our [integration page](https://app.lemlist.com/settings/integrations). You need to add the `Authorization` header using the `Basic` authentication type. `login:password` **where the login is always empty and the password is the API key**. ⚠️ **Don't forget to add the semicolon (**`:`**) before your API key in curl command.** > To authorize, use this code: ``` shell curl https://api.lemlist.com/api/team \ --user ":YourApiKey" ``` **Make sure to replace** **`YourApiKey`** **with your API key.** # Give feedback If you want to report a bug, ask for data, or share with us a use case, please fill this [form](https://lemlist.typeform.com/to/mfVlkyGf). It will help us centralize your needs! servers: - url: https://api.lemlist.com/api security: - basicAuth: [] tags: - name: Enrichment Providers description: >- The data providers lemlist can call to find an email or a phone. Internal providers are paid with lemlist credits and always available. External providers run on your own account: connect one by saving its API key, and it becomes available to your waterfalls. `GET /enrichments/providers` is the catalog of provider ids accepted by the waterfall endpoints. - name: Enrichment Waterfalls description: >- Control which data providers lemlist calls when enriching a contact, and in which order. A waterfall is an ordered list of providers for one enrichment `type` (`email` or `phone`). Providers are tried one after the other until one returns a result. Every team has exactly one default waterfall per type (`isDefault: true`). While its `editor` is `lemlist` it follows the lemlist behaviour: providers you connected with your own API key are tried first, then internal providers in a random order. Once a team member edits its provider list, `editor` becomes that user's id and the list is followed as is; resetting it hands it back to `lemlist`. Custom waterfalls (`isDefault: false`) carry `conditions` on the contact being enriched, keyed by contact property; every key present must match. When a contact is enriched, lemlist runs a single waterfall: the custom waterfall of the requested type whose conditions match the contact, or the default waterfall when none does. If several match, the one with the most condition keys wins, then the most recently updated. Only that waterfall runs; when it finds nothing, the enrichment ends without falling back to another one. paths: /tasks: get: tags: - Tasks summary: Get Many Tasks description: >- Retrieve tasks with optional filtering and pagination. Tasks marked as `done` are excluded from results. parameters: - name: page in: query description: Page number for paginated results (0-indexed). required: false schema: type: integer default: 0 - name: filters in: query description: >- JSON array of filter objects. Each filter has a `filterId` and specific parameters. **Available Filters:** - `fullName`: Filter by contact's full name. - Parameters: `value` (string) or `regex` (string) - Example: `{"filterId":"fullName","value":"John Doe"}` - `email`: Filter by contact's email address. - Parameters: `value` (string) or `regex` (string) - Example: `{"filterId":"email","value":"john@example.com"}` - `phone`: Filter by contact's phone number. - Parameters: `value` (string) or `regex` (string) - Example: `{"filterId":"phone","value":"+1234567890"}` - `linkedin`: Filter by LinkedIn profile URL. - Parameters: `value` (string) or `regex` (string) - Example: `{"filterId":"linkedin","value":"linkedin.com/in/johndoe"}` - `campaignId`: Filter by campaign IDs (inclusion/exclusion). - Parameters: `in` (array of strings) and/or `out` (array of strings) - Example: `{"filterId":"campaignId","in":["cam_123"],"out":["cam_456"]}` - `campaignState`: Filter by campaign states. - Parameters: `in` (array of strings) and/or `out` (array of strings) - Allowed values: `draft`, `running`, `ended`, `paused`, `errors`, `archived` - Example: `{"filterId":"campaignState","in":["running","paused"]}` - `type`: Filter by task type. - Parameters: `in` (array of strings) and/or `out` (array of strings) - Allowed values: `manual`, `phone`, `linkedinInvite`, `linkedinSend`, `linkedinVoiceNote`, `emailsReplied`, `opportunityReplied`, `linkedinReplied`, `opportunityClicked`, `email`, `whatsappMessage` - Example: `{"filterId":"type","in":["phone","email"]}` - `assignedTo`: Filter by assigned user IDs. - Parameters: `in` (array of strings) and/or `out` (array of strings) - Example: `{"filterId":"assignedTo","in":["usr_123","usr_456"]}` - `dueDate`: Filter by due date range. - Parameters: `from` (string, YYYY-MM-DD) and/or `to` (string, YYYY-MM-DD) - Example: `{"filterId":"dueDate","from":"2025-01-01","to":"2025-12-31"}` Multiple filters can be combined in an array. required: false schema: type: string example: >- [{"filterId":"dueDate","from":"2025-02-11","to":"2025-02-28"},{"filterId":"type","in":["phone","linkedinSend"]}] responses: '200': description: Success content: application/json: schema: type: object properties: results: type: array items: allOf: - $ref: '#/components/schemas/Task' - type: object properties: campaign: type: object nullable: true description: >- Campaign of the task, or `null` when the task has none. properties: id: type: string description: Campaign ID name: type: string description: >- Campaign name, or its ID when the campaign has no name sequenceId: type: string nullable: true description: Sequence ID of the campaign, or `null` ownerName: type: string nullable: true description: >- First and last name of the assigned user, or `null` when unknown. page: oneOf: - type: string - type: integer description: >- Value of the `page` query parameter, as sent (a string). The number `0` when the parameter is omitted. example: results: - _id: opp_LyXDV8KHzctQdLFpG type: manual title: Keep an eye on him priority: 1 leadId: lea_fiDpiGV585wy3Oii2 campaignId: cam_bSn8EORHQxbWPjHvu contactId: ctc_xW8Ou6C03Csv8vatp dueDate: '2025-11-10T09:58:57.169Z' userId: usr_ahfFktBBHUIxbVG5P content: does he have bandwidth to help us? would be grand campaign: id: cam_bSn8EORHQxbWPjHvu name: Acme outreach sequenceId: seq_9brn1aEKdYbDerkqq ownerName: John Doe - _id: opp_KNQOrrlGnLvEXDDS9 type: manual title: API Reference Illustration priority: 2 dueDate: '2025-10-31T07:58:00.000Z' userId: usr_ahfFktBBHUIxbVG5P content: '' campaign: null ownerName: John Doe page: '0' '400': description: Bad team content: text/plain: example: Bad team '401': description: The authentication you supplied is incorrect content: text/plain: example: The authentication you supplied is incorrect deprecated: true components: schemas: Task: type: object description: >- A manual action assigned to a user to complete. Only the fields set on the task are returned. properties: _id: type: string description: Unique task identifier type: type: string description: >- Task type as stored, never `null`. Tasks created through the API use `email`, `manual`, `phone`, `linkedinSend` or `whatsappMessage`. Campaign tasks carry the type of their step (for example `linkedinInvite`, `whatsappVoiceNote` or `sms`), and reply and click tasks use `opportunityReplied` and `opportunityClicked`. title: type: string description: Task title content: type: string description: >- Task instruction, sent as `message` when the task is created or updated. text: type: string description: >- Text of the lead's LinkedIn reply, when it has one, on `opportunityReplied` tasks. priority: type: integer enum: - 0 - 1 - 2 description: '`0` low, `1` medium, `2` high. Absent when the task has no priority.' dueDate: type: string format: date-time description: Due date. Tasks carry no creation date. userId: type: string description: ID of the assigned user, sent as `assignedTo`. leadId: type: string description: Associated lead ID contactId: type: string description: Associated contact ID campaignId: type: string description: Campaign ID. A task on a lead carries the campaign of that lead. sequenceId: type: string description: Sequence ID leadFirstName: type: string description: First name of the lead or contact leadLastName: type: string description: Last name of the lead or contact leadCompanyName: type: string description: >- Company name of the lead or contact. On a company task, the name (or domain) of the company, the only field that identifies it: the response carries no `companyId`. manual: type: boolean description: >- `true` on tasks created by hand in lemlist or through the API, on campaign tasks whose step has its manual option on, and on out-of-office tasks. Absent otherwise, never `false`. securitySchemes: basicAuth: type: http scheme: basic ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.