> ## 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 your team's deliverability incidents, newest first, active and resolved. # List Deliverability Incidents > [!NOTE] > > This endpoint uses the [Deliverability incident object](/api-reference/objects-definitions/deliverability-incident). > [!NOTE] > > Alert types turned off in your team's Notifications settings (Deliverability > Alerts) are never returned. Resolved incidents are kept 90 days. > [!WARNING] > > This endpoint is in closed beta. It answers `403` with the code `BETA_NOT_ENABLED` unless the deliverability incidents beta is enabled for your team. ## OpenAPI ````yaml get /deliverability/incidents 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: /deliverability/incidents: get: tags: - Deliverability alerts summary: List Deliverability Incidents description: >- Lists your team's deliverability incidents, newest first: DNS issues that lock sending, mailboxes disconnected from lemlist, mailboxes disconnected while warming up, and warm-ups paused by lemwarm. An incident stays `active` until the issue clears, then becomes `resolved` with a `resolvedAt` date. Alert types turned off in your team's Notifications settings (Deliverability > Alerts) are never returned. Resolved incidents are kept 90 days. This endpoint is in closed beta and answers `403` unless the beta is enabled for your team. operationId: listDeliverabilityIncidents parameters: - name: type in: query required: false description: Only incidents of this type. schema: type: string enum: - dnsIssue - mailboxDisconnected - lemwarmDisconnected - lemwarmPaused example: dnsIssue - name: state in: query required: false description: >- `active`: the issue is still there. `resolved`: it cleared. Omit for both. schema: type: string enum: - active - resolved example: active - name: userId in: query required: false description: Only incidents on mailboxes owned by this teammate. schema: type: string example: usr_Example3Hd8Pv5Rt1 - name: since in: query required: false description: >- Only incidents detected at or after this date or instant (ISO 8601; a date-time needs its offset). schema: type: string example: '2026-10-01' - name: until in: query required: false description: >- Only incidents detected at or before this date or instant (ISO 8601; a date-time needs its offset). schema: type: string example: '2026-10-31T23:59:59Z' - name: limit in: query required: false description: Maximum number of incidents to return. schema: type: integer minimum: 1 maximum: 100 default: 20 - name: skip in: query required: false description: Number of incidents to skip, for pagination. schema: type: integer minimum: 0 default: 0 responses: '200': description: Success content: application/json: schema: type: object properties: data: type: object properties: incidents: type: array items: $ref: '#/components/schemas/DeliverabilityIncident' total: type: integer description: >- Number of incidents matching the filters, across all pages example: data: incidents: - _id: dli_A1B2C3D4E5F6G7H8J userId: usr_Example3Hd8Pv5Rt1 userMailboxId: usm_FakeQ4Lz7Nb2Xc9Vj mailboxEmail: john@example.com type: dnsIssue state: active message: |- SPF record missing for example.com DMARC record missing for example.com openedAt: '2026-10-07T16:23:00.000Z' total: 1 '400': description: Validation error - a query parameter has an invalid value content: application/json: schema: $ref: '#/components/schemas/DeliverabilityIncidentError' example: error: >- Invalid query parameters: check type, state, userId, since, until, limit and skip. code: DELIVERABILITY_INCIDENT_INVALID_INPUT '401': description: Unauthorized - invalid or missing API key content: application/json: schema: $ref: '#/components/schemas/DeliverabilityIncidentError' example: error: Route unauthorized code: ROUTE_UNAUTHORIZED '403': description: The beta is not enabled for your team content: application/json: schema: $ref: '#/components/schemas/DeliverabilityIncidentError' example: error: Beta is not enabled code: BETA_NOT_ENABLED '405': description: Method not allowed - only GET is supported content: application/json: schema: $ref: '#/components/schemas/DeliverabilityIncidentError' example: error: Route bad method code: ROUTE_BAD_METHOD '500': description: Internal server error content: application/json: schema: $ref: '#/components/schemas/DeliverabilityIncidentError' example: error: Internal error code: INTERNAL_ERROR components: schemas: DeliverabilityIncident: type: object description: >- One deliverability problem on one of your mailboxes. It opens when the problem is detected and resolves when the mailbox recovers. properties: _id: type: string description: Unique identifier of the incident userId: type: string description: Owner of the mailbox userMailboxId: type: string description: Mailbox the incident is about mailboxEmail: type: string description: Sending address of the mailbox type: type: string enum: - dnsIssue - mailboxDisconnected - lemwarmDisconnected - lemwarmPaused description: >- `dnsIssue`: an SPF, DMARC, MX or custom tracking domain check failed, so sending is locked. `mailboxDisconnected`: lemlist lost access to the mailbox. `lemwarmDisconnected`: the mailbox was disconnected while warming up, so warm-up stopped. `lemwarmPaused`: lemwarm paused the warm-up after a bounce or a sending failure. state: type: string enum: - active - resolved description: '`active` while the problem lasts, `resolved` once it cleared' code: type: string description: Error code reported by the provider or by lemwarm, when known message: type: string description: Plain-text explanation of the problem, when known openedAt: type: string format: date-time description: When the problem was detected resolvedAt: type: string format: date-time description: When the problem cleared. Absent while `active` DeliverabilityIncidentError: type: object description: Error envelope returned by the deliverability incidents endpoint. 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.