> ## 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. > Updates the daily LinkedIn limits (invitations, messages, profile visits, InMails, endorsements and more) and the invite ramp-up of a team member. # Update User LinkedIn Limits Requires the permission to edit sending limits and a paid plan. The user must be a member of the team the API key belongs to. ## OpenAPI ````yaml patch /users/{userId}/linkedin-limits 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: /users/{userId}/linkedin-limits: patch: tags: - Users summary: Update User LinkedIn Limits parameters: - name: userId in: path required: true description: ID of the team member whose LinkedIn limits to update (usr_xxx) schema: type: string requestBody: description: >- The team member's daily LinkedIn limits to change, named like the `linkedIn` limits of GET /users/{userId}. Provide only the fields you want to change; omitted ones keep their current value. At least one is required, and unknown fields are refused: an invalid body fails the whole update and nothing is written. Same limits as Settings > Sending limits: a value above the recommended maximum is stored and the response carries a warning. content: application/json: schema: type: object minProperties: 1 additionalProperties: false properties: followLimit: type: integer minimum: 1 description: Max LinkedIn follows per day inviteLimit: type: integer minimum: 1 description: Max LinkedIn invitations per day sendLimit: type: integer minimum: 1 description: Max LinkedIn direct messages per day visitLimit: type: integer minimum: 1 description: Max LinkedIn profile visits per day inMailLimit: type: integer minimum: 1 description: >- Max LinkedIn InMails per day: a daily throttle, the monthly InMail credits of the LinkedIn plan stay the hard cap networkCheckLimit: type: integer minimum: 1 description: Max LinkedIn network checks per day withdrawInvitationLimit: type: integer minimum: 1 description: Max LinkedIn invitation withdrawals per day likeLastPostLimit: type: integer minimum: 1 description: Max LinkedIn last-post likes per day endorseLimit: type: integer minimum: 1 description: Max LinkedIn endorsements per day commentLastPostRetrieveLimit: type: integer minimum: 1 description: Max LinkedIn last-post retrievals per day commentLastPostSendLimit: type: integer minimum: 1 description: Max LinkedIn last-post comments per day inviteRampUp: type: integer nullable: true minimum: 1 description: >- Invite ramp-up: how much the daily invitation limit grows each day until it reaches inviteLimit. null turns the ramp-up off; omit it to keep it as is example: inviteLimit: 35 inMailLimit: 8 inviteRampUp: 3 responses: '200': description: >- Every daily LinkedIn limit and the invite ramp-up of the team member after the update content: application/json: schema: type: object properties: data: type: object properties: userId: type: string description: ID of the team member (usr_xxx) followLimit: type: integer description: Max LinkedIn follows per day inviteLimit: type: integer description: Max LinkedIn invitations per day sendLimit: type: integer description: Max LinkedIn direct messages per day visitLimit: type: integer description: Max LinkedIn profile visits per day inMailLimit: type: integer description: >- Max LinkedIn InMails per day: a daily throttle, the monthly InMail credits of the LinkedIn plan stay the hard cap networkCheckLimit: type: integer description: Max LinkedIn network checks per day withdrawInvitationLimit: type: integer description: Max LinkedIn invitation withdrawals per day likeLastPostLimit: type: integer description: Max LinkedIn last-post likes per day endorseLimit: type: integer description: Max LinkedIn endorsements per day commentLastPostRetrieveLimit: type: integer description: Max LinkedIn last-post retrievals per day commentLastPostSendLimit: type: integer description: Max LinkedIn last-post comments per day inviteRampUp: type: integer nullable: true description: >- Invite ramp-up: how much the daily invitation limit grows each day until it reaches inviteLimit; null when the ramp-up is off warning: type: string description: >- Present when a value written is above its recommended daily maximum; names each such field with its maximum. The value is stored anyway, LinkedIn may restrict the account example: data: userId: usr_Q7mT2vLx9KpR4nWbZ followLimit: 20 inviteLimit: 35 sendLimit: 30 visitLimit: 30 inMailLimit: 8 networkCheckLimit: 30 withdrawInvitationLimit: 30 likeLastPostLimit: 30 endorseLimit: 20 commentLastPostRetrieveLimit: 20 commentLastPostSendLimit: 20 inviteRampUp: 3 warning: >- Above the recommended daily maximum: inviteLimit (30); LinkedIn may restrict the account '400': description: >- Malformed userId, invalid body (unknown field, non-positive or non-integer value), or nothing to update (`LINKEDIN_LIMITS_NOTHING_TO_UPDATE`) content: application/json: example: error: >- Send only LinkedIn limits named like GET /api/users/:userId (e.g. inviteLimit, inMailLimit), as positive integers code: LINKEDIN_LIMITS_INVALID_INPUT '401': description: The API key does not resolve a user '402': description: The team is on a free trial or has no lemlist plan content: application/json: example: error: You cannot change the LinkedIn limits during free trial. code: LINKEDIN_LIMITS_NO_PAID_PLAN '403': description: The user lacks the permission to edit sending limits content: application/json: example: error: You cannot edit sending limits for this team code: LINKEDIN_LIMITS_PERMISSION_DENIED '404': description: The user is not a member of the team content: application/json: example: error: This user is not a member of your team code: LINKEDIN_LIMITS_USER_NOT_IN_TEAM '405': description: Method other than PATCH '500': description: Internal server error content: application/json: example: error: Internal error code: INTERNAL_ERROR components: securitySchemes: basicAuth: type: http scheme: basic ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.