> ## 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. # List Self-recovery History > Lists your team's self-recovery incident history, most recent first. Each case captures a detected degradation and the recommendations self-recovery made or executed. > [!NOTE] > > This endpoint uses the [Self-recovery case object](https://developer.lemlist.com/api-reference/objects-definitions/self-recovery-case.md). ## OpenAPI ````yaml get /self-recovery/history 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/history: get: tags: - Self-recovery summary: List Self-recovery History parameters: - name: limit in: query required: false description: Max cases to return (1-100). schema: type: integer minimum: 1 maximum: 100 - name: skip in: query required: false description: Number of cases to skip, for pagination. schema: type: integer minimum: 0 responses: '200': description: Success content: application/json: schema: type: object properties: history: type: array items: $ref: '#/components/schemas/SelfRecoveryCase' total: type: integer description: Total number of cases for the team. example: history: - _id: srh_ExampleAcmeCaseId teamId: tea_ExampleAcmeTeamId assetId: usm_ExampleMailboxId assetType: mailbox assetLabel: john@example.com openedAt: '2026-05-06T18:42:11.000Z' status: executed recommendations: - rootCause: reputationDecline strategy: recover action: recover confidence: medium explanationCode: reputationDecline explanationVars: [] contributingSignals: - bounceRate executionStatus: executed executedAt: '2026-05-06T18:42:11.000Z' previousEmailsLimit: 40 lastDiagnosisKey: reputationDecline|recover|recover total: 1 '401': description: Unauthorized components: schemas: SelfRecoveryCase: type: object description: >- A self-recovery incident case, opened when a monitored asset degrades. Append-only: one entry per trigger. properties: _id: type: string description: Case identifier (prefixed with `srh_`). teamId: type: string description: ID of the team that owns the case. assetId: type: string description: ID of the affected asset (a mailbox, prefixed with `usm_`). assetType: type: string enum: - mailbox description: Type of the affected asset. assetLabel: type: string description: Human-readable label for the asset (usually the mailbox email). openedAt: type: string format: date-time description: When the case was opened. status: type: string enum: - recommended - executed description: >- `recommended` when nothing ran (no authorized + wired action); `executed` when at least one recommendation was applied. recommendations: type: array items: $ref: '#/components/schemas/SelfRecoveryRecommendation' description: Ordered list of recommended fixes (primary first). lastDiagnosisKey: type: string description: Internal key used to dedup identical diagnoses across ticks. SelfRecoveryRecommendation: type: object description: >- A single recommended fix produced by the diagnosis. A case can carry several. properties: rootCause: type: string description: Diagnosed root cause of the degradation. enum: - dnsAuthentication - listQuality - senderReputation - reputationDecline - inconclusive strategy: type: string description: Recommended recovery strategy (the "what"). enum: - fixDns - listHygiene - replace - provision - recover - none action: type: string description: Concrete asset-level action the strategy executes. enum: - pause - replace - provision - recover - none confidence: type: string enum: - low - medium - high explanationCode: type: string description: Stable code for the explanation text, resolved client-side. explanationVars: type: array items: type: string description: Ordered substitutions for the explanation text. contributingSignals: type: array items: type: string enum: - bounceRate - blacklist - inboxPlacement description: Signals that contributed to this recommendation. executionStatus: type: string description: Automatic-execution outcome. Absent on pre-execution entries. enum: - executed - skippedNotAuthorized - notExecutable - failed executedAt: type: string format: date-time description: When the action ran. executionDetail: type: string description: >- Machine-readable outcome detail (e.g. `already-locked`, `limit-already-low`, `lemwarm:`). previousEmailsLimit: type: integer description: 'recover only: the daily sending limit before the volume cooldown.' securitySchemes: basicAuth: type: http scheme: basic ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.