> ## 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 validation statutes for a campaign, including errors that block launching and warnings about daily limits, DNS issues, etc.

# Get Campaign Statutes

Statutes use the same validation engine as the lemlist UI. Each statute has a severity level:

| Level | Meaning                               | Example                                     |
| ----- | ------------------------------------- | ------------------------------------------- |
| **3** | Error — blocks campaign launch        | Invalid sender, missing mailbox, broken DNS |
| **2** | Warning — actionable but not blocking | Daily limit exceeded, schedule missing      |
| **1** | Info — purely informational           | Sending rate summary                        |


## OpenAPI

````yaml get /campaigns/{campaignId}/statutes
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:
  /campaigns/{campaignId}/statutes:
    parameters:
      - name: campaignId
        in: path
        required: true
        description: The unique identifier of the campaign
        example: cam_A1B2C3D4E5F6G7H8I9
        schema:
          type: string
    get:
      tags:
        - Campaigns
      summary: Get Campaign Statutes
      description: >-
        Retrieves validation statutes for a campaign, including errors that
        block launching and warnings about daily limits, DNS issues, etc. Uses
        the same validation engine as the lemlist UI.
      parameters: []
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                properties:
                  name:
                    type: string
                    description: The campaign name
                  status:
                    type: string
                    description: The campaign status (draft, running, paused, etc.)
                  statutes:
                    type: array
                    description: List of validation statutes for the campaign
                    items:
                      type: object
                      properties:
                        type:
                          type: string
                          enum:
                            - issue
                            - information
                          description: >-
                            Statute type: 'issue' for problems, 'information'
                            for non-blocking info
                        level:
                          type: integer
                          enum:
                            - 1
                            - 2
                            - 3
                          description: >-
                            Severity: 3 = error (blocks launch), 2 = warning
                            (actionable), 1 = info
                        message:
                          type: string
                          description: >-
                            Human-readable description of the issue (may contain
                            HTML)
                        category:
                          type: string
                          description: >-
                            Optional category (e.g. 'limit', 'steps',
                            'schedule')
              example:
                name: Product Launch Campaign
                status: draft
                statutes:
                  - type: issue
                    level: 3
                    message: No senders configured on this campaign.
                  - type: information
                    level: 2
                    category: limit
                    message: >-
                      John Doe daily email sending limit has been exceeded. You
                      can increase the limit in settings or wait 2 hours
        '400':
          description: Bad team
          content:
            text/plain:
              example: Bad team
        '401':
          description: Unauthorized
        '404':
          description: Campaign not found
        '405':
          description: Bad method
components:
  securitySchemes:
    basicAuth:
      type: http
      scheme: basic

````