> ## 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. > Removes the API key of an external enrichment provider; lemlist stops calling it on your account. # Disconnect Provider Connected providers show `connected: true` in [List Enrichment Providers](/api-reference/endpoints/enrichment-providers/list-enrichment-providers). ## OpenAPI ````yaml delete /v2/enrichments/providers/{providerId}/connection 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: /v2/enrichments/providers/{providerId}/connection: parameters: - name: providerId in: path required: true description: Id of an external provider, as listed by `GET /enrichments/providers`. schema: type: string example: lusha delete: tags: - Enrichment Providers summary: Disconnect Provider description: >- Removes your API key for an external provider. lemlist stops calling it on your account and removes it from your custom waterfalls. operationId: disconnectEnrichmentProvider responses: '200': description: Success content: application/json: schema: $ref: '#/components/schemas/EnrichmentProviderResponse' example: data: id: lusha displayName: Lusha types: - email - phone source: external connected: false '400': description: >- The provider is internal or not connected. `code` is one of `ENRICHMENT_PROVIDER_NOT_EXTERNAL`, `ENRICHMENT_PROVIDER_NOT_CONNECTED`. content: application/json: schema: $ref: '#/components/schemas/EnrichmentWaterfallError' example: error: Provider "apollo" is not connected code: ENRICHMENT_PROVIDER_NOT_CONNECTED '401': $ref: '#/components/responses/EnrichmentWaterfallUnauthorized' '500': $ref: '#/components/responses/EnrichmentWaterfallInternalError' components: schemas: EnrichmentProviderResponse: type: object properties: data: $ref: '#/components/schemas/EnrichmentProvider' EnrichmentWaterfallError: type: object description: Error envelope returned by the enrichment waterfall endpoints. properties: error: type: string description: Human-readable explanation of the failure code: type: string description: Machine-readable error code, stable across releases EnrichmentProvider: type: object description: A data provider your team can place in a waterfall. required: - id - displayName - types - source properties: id: type: string description: >- Stable identifier, to use as `providers[].id` in the waterfall endpoints. example: prospeo displayName: type: string description: Name shown in the lemlist app. example: Prospeo types: type: array description: Enrichment types this provider supports. items: $ref: '#/components/schemas/EnrichmentWaterfallType' source: type: string description: >- `internal`: paid with lemlist credits, always available. `external`: called with your own API key, saved through the connection endpoint. enum: - internal - external connected: type: boolean description: >- Only on external providers: `true` once its API key is saved in lemlist. A waterfall can only enable a connected provider. EnrichmentWaterfallType: type: string description: Kind of data the waterfall looks for. enum: - email - phone responses: EnrichmentWaterfallUnauthorized: description: Unauthorized - invalid or missing API key content: application/json: schema: $ref: '#/components/schemas/EnrichmentWaterfallError' example: error: Route unauthorized code: ROUTE_UNAUTHORIZED EnrichmentWaterfallInternalError: description: Internal server error content: application/json: schema: $ref: '#/components/schemas/EnrichmentWaterfallError' example: error: Internal error code: INTERNAL_ERROR securitySchemes: basicAuth: type: http scheme: basic ````