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

> Lists all non-deleted drafts for a specific contact.

# List Drafts

<Note>
  The `draftOwner` query parameter is required and identifies the draft owner. It accepts either:

  * A **userId** (e.g., `usr_abc123def456789`) — used directly
  * A **login email** (e.g., `john@acme.com`) — resolved to userId via email lookup

  This follows the same pattern as `contactOwner` in the Lead API. Team membership is verified in both cases.
</Note>


## OpenAPI

````yaml get /inbox/{contactId}/drafts
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:
  /inbox/{contactId}/drafts:
    get:
      tags:
        - Inbox
      summary: List Drafts
      description: Lists all non-deleted drafts for a specific contact.
      parameters:
        - name: contactId
          in: path
          required: true
          description: Contact ID
          example: ctc_ei6zVayP9B2ugwUPN
          schema:
            type: string
        - name: draftOwner
          in: query
          required: true
          description: >-
            Draft owner identifier. Accepts either a userId (e.g.,
            `usr_abc123def456789`) or a login email (e.g., `john@acme.com`).
          example: usr_abc123def456789
          schema:
            type: string
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                properties:
                  drafts:
                    type: array
                    items:
                      type: object
                      properties:
                        _id:
                          type: string
                          description: Unique draft identifier
                        channel:
                          type: string
                          enum:
                            - email
                            - linkedin
                            - whatsapp
                            - sms
                          description: Communication channel
                        subject:
                          type: string
                          description: Draft subject
                        contentPreview:
                          type: string
                          description: Content preview (max 100 chars)
                        source:
                          type: string
                          enum:
                            - api
                            - ui
                          description: Draft creation source
                        createdAt:
                          type: string
                          format: date-time
                          description: Creation date
                        updatedAt:
                          type: string
                          format: date-time
                          description: Last update date
              example:
                drafts:
                  - _id: drf_abc123def456789
                    channel: email
                    subject: Follow up on our meeting
                    contentPreview: >-
                      Hi John, I wanted to follow up on our conversation from
                      last week...
                    source: api
                    createdAt: '2025-01-15T10:30:00.000Z'
                    updatedAt: '2025-01-15T10:30:00.000Z'
        '400':
          description: 'Possible errors: Missing draftOwner / User not found'
          content:
            text/plain:
              example: >-
                User not found: neither a valid email nor a valid user id for
                this team
        '401':
          description: The authentication you supplied is incorrect
          content:
            text/plain:
              example: The authentication you supplied is incorrect
        '405':
          description: Method not allowed
components:
  securitySchemes:
    basicAuth:
      type: http
      scheme: basic

````