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

# Set View Tabs

> Sets which views show as the API key user's tabs on a list, and in which order.



## OpenAPI

````yaml put /views/tabs
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:
  /views/tabs:
    put:
      tags:
        - Views
      summary: Set View Tabs
      description: >-
        Sets the API key user's tabs on one list: the views in `pinned` show as
        tabs, in that order. Every other view is hidden from the tabs, not
        deleted, and stays in the views panel. Tabs are personal: other members
        keep theirs.


        Every id must be one of the views the user sees on that list, default
        views included; a repeated id counts once.
      operationId: setViewTabs
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              additionalProperties: false
              required:
                - entity
                - pinned
              properties:
                entity:
                  $ref: '#/components/schemas/ViewEntity'
                pinned:
                  type: array
                  maxItems: 200
                  description: Ids of the views to show as tabs, in tab order
                  items:
                    type: string
                    minLength: 1
                    maxLength: 64
            example:
              entity: contact
              pinned:
                - evw_A1B2C3ExAmPlE9xYz
                - evw_contact_my_contacts
      responses:
        '200':
          description: Tabs saved
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: object
                    required:
                      - pinned
                    properties:
                      pinned:
                        type: array
                        items:
                          type: string
                        description: The tabs, in order
              example:
                data:
                  pinned:
                    - evw_A1B2C3ExAmPlE9xYz
                    - evw_contact_my_contacts
        '400':
          description: Invalid body
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ViewError'
              example:
                error: Validation error
                code: VALIDATION_ERROR
        '401':
          description: >-
            Unauthorized - invalid or missing API key. An API key with no user
            attached answers `{ "error": "Route unauthorized", "code":
            "ROUTE_UNAUTHORIZED" }` in JSON instead.
          content:
            text/plain:
              example: The authentication you supplied is incorrect
        '403':
          description: That list's views are not enabled for your team
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ViewError'
              example:
                error: Views of this list are not enabled for this team
                code: ENTITY_VIEW_ENTITY_UNAVAILABLE
        '404':
          description: An id is not one of the views the user sees on that list
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ViewError'
              example:
                error: View not found
                code: ENTITY_VIEW_NOT_FOUND
components:
  schemas:
    ViewEntity:
      type: string
      enum:
        - contact
        - company
        - task
      description: >-
        The list a view belongs to: `contact` (Contacts page), `company`
        (Companies page) or `task` (Tasks page)
      example: contact
    ViewError:
      type: object
      description: Error envelope returned by the views endpoints.
      properties:
        error:
          type: string
          description: Human-readable explanation of the failure
        code:
          type: string
          description: Machine-readable error code, stable across releases
  securitySchemes:
    basicAuth:
      type: http
      scheme: basic

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.