> ## 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. # Update Self-recovery Config > Updates your team's self-recovery configuration. Every field is optional; only the fields you send are changed. > [!NOTE] > > This endpoint uses the [Self-recovery config object](https://developer.lemlist.com/api-reference/objects-definitions/self-recovery-config.md). ## What you can change * `enabled` — turn self-recovery on or off for the account. * `monitoredSignals` — the signals self-recovery watches. This **replaces** the current list, so send the full set, not a delta. `inboxPlacement` requires the inbox-placement test to be active on the account. * `authorizedActions` — the strategies self-recovery may run automatically. This **replaces** the current list. * `digestFrequency` — how often team admins get the recovery summary email: `daily`, or `weekly` on Mondays. It is sent at 8am in the team timezone, and only when self-recovery opened a case. The first update creates the configuration; `digestFrequency` starts at `daily` unless you send it. ## Authorized actions Only `fixDns` and `recover` can be authorized: * `fixDns` — pause sending until the DNS records are corrected. * `recover` — cap the daily sending volume and re-warm the mailbox. `provision`, `replace` and `listHygiene` are diagnosis-only: self-recovery will still recommend them in the history, but it never executes them automatically. Sending any of them in `authorizedActions` returns `400`. ## OpenAPI ````yaml patch /self-recovery/config 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: /self-recovery/config: patch: tags: - Self-recovery summary: Update Self-recovery Config requestBody: required: true description: >- All fields are optional; only the supplied fields change. `monitoredSignals` and `authorizedActions` replace the current lists (send the full set). Only `fixDns` and `recover` may be authorized. The first update creates the configuration, with `digestFrequency` set to `daily` unless you send it. content: application/json: schema: type: object properties: enabled: type: boolean description: Turn self-recovery on or off. monitoredSignals: type: array items: type: string enum: - bounceRate - blacklist - inboxPlacement description: Replaces the monitored-signals list. authorizedActions: type: array items: type: string enum: - fixDns - recover description: >- Replaces the authorized-actions list. Only fixDns and recover are accepted. digestFrequency: type: string enum: - daily - weekly description: >- How often team admins get the recovery summary email: daily, or weekly on Mondays. example: monitoredSignals: - bounceRate - blacklist authorizedActions: - recover digestFrequency: weekly responses: '200': description: Success content: application/json: schema: type: object properties: config: $ref: '#/components/schemas/SelfRecoveryConfig' example: config: _id: src_ExampleAcmeConfigId teamId: tea_ExampleAcmeTeamId enabled: true monitoredSignals: - bounceRate - blacklist authorizedActions: - recover digestFrequency: weekly createdBy: usr_ExampleAcmeUserId createdAt: '2026-04-12T09:30:00.000Z' updatedAt: '2026-05-06T14:10:00.000Z' '400': description: Invalid input '401': description: Unauthorized components: schemas: SelfRecoveryConfig: type: object description: >- Account-level self-recovery configuration. Self-recovery watches the monitored signals and, when authorized, automatically runs recovery actions on degraded mailboxes. properties: _id: type: string description: Config identifier (prefixed with `src_`). teamId: type: string description: ID of the team that owns the config. enabled: type: boolean description: Whether self-recovery is active for the account. monitoredSignals: type: array items: type: string enum: - bounceRate - blacklist - inboxPlacement description: >- Signals self-recovery watches. `inboxPlacement` requires the placement test to be active. authorizedActions: type: array items: type: string enum: - fixDns - recover description: >- Strategies self-recovery may execute automatically. Only `fixDns` and `recover` can be authorized; `provision`, `replace` and `listHygiene` are diagnosis-only and rejected here. digestFrequency: type: string enum: - daily - weekly description: >- How often team admins get the recovery summary email: `daily`, or `weekly` on Mondays. Sent at 8am in the team timezone, only when self-recovery opened a case. Absent on configs created before this setting existed, which get the `daily` digest. createdBy: type: string description: ID of the user who created the config. createdAt: type: string format: date-time description: Creation timestamp. updatedAt: type: string format: date-time description: Last update timestamp. securitySchemes: basicAuth: type: http scheme: basic ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.