> ## 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 the distinct tags of the team's library message templates, alphabetically.

# List Message Template Tags

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="Message template" objectPath="message-template" />

Use it to discover the values `tags` accepts on
[List message templates](/api-reference/endpoints/message-templates/list-message-templates).
Tags are stored trimmed and lowercased; pass them back as returned.

<Note>
  `search` matches inside the tag, case-insensitive, accents folded on
  `a c e i n o u y`. `userIds` keeps the tags of those creators' templates only.
  Each item is an object (`{ "name": "follow-up" }`) so a per-tag count can be
  added later without changing the contract.
</Note>


## OpenAPI

````yaml get /message-templates/tags
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:
  /message-templates/tags:
    get:
      tags:
        - Message templates
      summary: List Message Template Tags
      description: >-
        Lists the distinct tags used on the team's library message templates,
        alphabetically. `search` matches inside the tag; `userIds` keeps the
        tags of those creators' templates only.
      parameters:
        - name: search
          in: query
          required: false
          description: >-
            Substring of the name, case-insensitive. Accented a, c, e, i, n, o,
            u, y match their plain letters (`relance` finds `Rélance`). Names
            only: bodies and subjects are not searched. Maximum 100 characters;
            a blank value is no filter.
          example: follow-up
          schema:
            type: string
            maxLength: 100
        - name: userIds
          in: query
          required: false
          description: >-
            Keep the items created by any of these users (`usr_` ids, see GET
            /team/members). Comma-separated; the parameter may also be repeated.
            Maximum 100. Omit for every creator.
          example: usr_A1B2C3D4E5F6G7H8I
          schema:
            type: string
        - name: page
          in: query
          required: false
          description: Page number to retrieve, starting at 1
          example: '1'
          schema:
            type: integer
            minimum: 1
            default: 1
        - name: limit
          in: query
          required: false
          description: 'Number of items per page. Maximum value: 100'
          example: '50'
          schema:
            type: integer
            minimum: 1
            maximum: 100
            default: 50
      responses:
        '200':
          description: >-
            One page of results, with the pagination block. An empty result is
            page 1 of 1.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MessageTemplateTagListResponse'
              example:
                data:
                  - name: follow-up
                  - name: pricing
                meta:
                  pagination:
                    page: 1
                    limit: 50
                    totalRecords: 1
                    totalPages: 1
        '400':
          description: >-
            `VALIDATION_ERROR` - a filter cap or a bad `page` / `limit` (JSON
            body), or no API key was supplied (plain text).
          content:
            application/json:
              example:
                error: Validation error
                code: VALIDATION_ERROR
            text/plain:
              example: no api key provided
        '401':
          description: >-
            Unauthorized - invalid or missing API key (plain text), or an API
            key with no linked user (JSON body carrying `ROUTE_UNAUTHORIZED`).
          content:
            text/plain:
              example: The authentication you supplied is incorrect
            application/json:
              example:
                error: Route unauthorized
                code: ROUTE_UNAUTHORIZED
        '405':
          description: Method not allowed - this endpoint only accepts GET
        '429':
          description: Rate limit exceeded - 20 requests per 2 seconds per API key
components:
  schemas:
    MessageTemplateTagListResponse:
      type: object
      properties:
        data:
          type: array
          items:
            $ref: '#/components/schemas/MessageTemplateTag'
        meta:
          $ref: '#/components/schemas/PageMeta'
    MessageTemplateTag:
      type: object
      description: >-
        One distinct tag of the library. An object, so a per-tag count can be
        added later without changing the contract.
      properties:
        name:
          type: string
          description: The tag, trimmed and lowercased
      example:
        name: follow-up
    PageMeta:
      type: object
      description: >-
        Pagination block of a list response. `totalPages` is at least 1: an
        empty result is page 1 of 1.
      properties:
        pagination:
          type: object
          properties:
            page:
              type: integer
              description: Current page number
            limit:
              type: integer
              description: Number of records per page
            totalRecords:
              type: integer
              description: Total records matching the filters
            totalPages:
              type: integer
              description: Total number of pages, at least 1
  securitySchemes:
    basicAuth:
      type: http
      scheme: basic

````