> ## 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. > Enriches an existing lead in lemlist with additional data. # Enrich Lead You can [enrich a lead](/api-reference/objects-definitions/enrich)with additional data. Check [enrich data](/api-reference/endpoints/enrich/enrich-data) for details on the enrichment result structure. ## OpenAPI ````yaml post /leads/{leadId}/enrich 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: [] paths: /leads/{leadId}/enrich: post: tags: - Enrich summary: Enrich Lead parameters: - name: leadId in: path required: true description: Unique lead ID example: lea_123 schema: type: string - name: findEmail in: query required: false description: Search email address in another campaign example: 'true' schema: type: boolean - name: verifyEmail in: query required: false description: Find verified email example: 'true' schema: type: boolean - name: linkedinEnrichment in: query required: false description: Run LinkedIn enrichment example: 'true' schema: type: boolean - name: findPhone in: query required: false description: Find phone number example: 'true' schema: type: boolean - name: webhookUrl in: query required: false description: Webhook URL for enrichment events example: https://n8n.example.com/webhook/lemlist-webhook-surprise schema: type: string - name: force in: query required: false description: >- Re-run an enrichment that would otherwise be skipped. Bypasses skips caused by data already present on the contact: existing email, existing phone, LinkedIn enrichment already done for the same `linkedinUrl` / `linkedinUrlSalesNav`, or email already having a deliverability status. Does **not** bypass: - **Enrichment currently in progress** — if another enrichment is already running for this contact, the request is still skipped (no parallel enrichments, no double billing). - **Previously returned not-found** — for `findEmail` and `findPhone`, if a prior enrichment with the same inputs (`linkedinUrl`, `linkedinUrlSalesNav`, first / last name, company name / domain / LinkedIn URL) already returned not-found, the request is still skipped. Changing any of those inputs on the lead lifts the block without needing `force`. example: 'true' schema: type: boolean responses: '200': description: Success content: application/json: schema: type: object properties: id: type: string description: Enrichment ID example: id: enr_Ohbs0mEsWmDjTnxTi '400': description: Bad team content: text/plain: example: Bad team '401': description: Unauthorized '404': description: Lead or contact not found content: application/json: examples: leadNotFound: summary: Lead does not exist value: error: Lead not found code: LEAD_NOT_FOUND contactNotFound: summary: Lead exists but its underlying contact is missing value: error: Contact not found for this lead code: CONTACT_NOT_FOUND '405': description: Method not allowed '409': description: >- Enrichment cannot proceed because of the current state of the lead/contact content: application/json: examples: alreadyEnriched: summary: >- Contact already has the requested data — retry with ?force=true to override value: error: >- Enrichment skipped: contact already has the requested data or was recently enriched code: ALREADY_ENRICHED inProgress: summary: >- An enrichment is already running for this lead — wait for it to complete value: error: lead is already being enriched '500': description: Enrichment failed content: application/json: example: error: Failed to enrich lead components: securitySchemes: basicAuth: type: http scheme: basic ````