> ## 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 <Note>
        This endpoint uses the <a href={`/api-reference/objects-definitions/${objectPath}`}>{objectName} object</a>. Make sure to also check the <a href={`/api-reference/objects-definitions/${lowerCaseObjectName === 'lead' ? 'contact' : 'lead'}`}>{lowerCaseObjectName === 'lead' ? 'Contact' : 'Lead'} object</a> to understand the distinction between the two.
      </Note>;
  }
  return <Note>
      This endpoint uses the <a href={`/api-reference/objects-definitions/${objectPath}`}>{objectName} object</a>.
    </Note>;
};

<SnippetObjectReference objectName="Task" objectPath="task" />

<Note>
  Tasks marked as done are automatically excluded from results.
</Note>

## 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:

<CodeGroup>
  ```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"]}]
  ```
</CodeGroup>


## 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: []
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:
                      $ref: '#/components/schemas/Task'
                  page:
                    type: string
              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
                  - _id: opp_KNQOrrlGnLvEXDDS9
                    type: manual
                    title: API Reference Illustration
                    priority: 2
                    dueDate: '2025-10-31T07:58:00.000Z'
                    userId: usr_ahfFktBBHUIxbVG5P
                    content: ''
                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
components:
  schemas:
    Task:
      type: object
      description: A manual action assigned to a user to complete.
      properties:
        _id:
          type: string
          description: Unique task identifier
        type:
          type: string
          description: Task type
        leadId:
          type: string
          description: Associated lead ID
        campaignId:
          type: string
          description: Campaign ID
        userId:
          type: string
          description: Assigned user ID
        status:
          type: string
          description: Task status
          enum:
            - pending
            - completed
            - ignored
        dueDate:
          type: string
          format: date-time
          description: Due date timestamp
        createdAt:
          type: string
          format: date-time
          description: Creation timestamp
        completedAt:
          type: string
          format: date-time
          description: Completion timestamp
  securitySchemes:
    basicAuth:
      type: http
      scheme: basic

````