> ## 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. > Retrieves one company by its lemlist id (`cpn_xxx`), as a bare object. Answers 404 when no company of your team carries this id. # Get Company export const SnippetObjectReference = ({objectName, objectPath = null}) => { const lowerCaseObjectName = objectName.toLowerCase(); if (lowerCaseObjectName === 'lead' || lowerCaseObjectName === 'leads') { return This endpoint uses the {objectName} object. Make sure to also check the {lowerCaseObjectName === 'lead' ? 'Contact' : 'Lead'} object to understand the distinction between the two. ; } return This endpoint uses the {objectName} object. ; }; Returns the company object itself, not a list. The endpoint answers `404 COMPANY_NOT_FOUND_BY_ID` when no company of your team carries this id, where `GET /companies?idsOrDomains=` answers `200` with an empty `data` array. Lookups by domain stay on `GET /companies?idsOrDomains=`: a domain is not guaranteed to designate a single company, so this endpoint takes ids only. ## OpenAPI ````yaml get /companies/{companyId} 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: /companies/{companyId}: get: tags: - Companies summary: Get Company description: >- Retrieves one lemlist company by its id (`cpn_xxx`) and returns the company object itself, unwrapped. Answers `404 COMPANY_NOT_FOUND_BY_ID` when no company of your team carries this id, where `GET /companies?idsOrDomains=` answers `200` with an empty `data` array. Lookups by domain stay on `GET /companies?idsOrDomains=`: a domain is not guaranteed to designate a single company, so this endpoint takes ids only. When a CRM is connected the company carries the `crmSync` block; `fieldRejections` lists the values lemlist refused to write on it. parameters: - name: companyId in: path required: true description: The lemlist company ID. example: cpn_A1B2C3D4E5F6G7H8I schema: type: string pattern: ^cpn_[a-zA-Z0-9]+$ responses: '200': description: The company. content: application/json: schema: $ref: '#/components/schemas/Company' example: _id: cpn_A1B2C3D4E5F6G7H8I teamId: tea_8QvkOiBfPdb2ZRhHi domain: acme.com linkedinUrl: https://www.linkedin.com/company/acme fields: name: Acme Corp industry: Technology location: San Francisco, CA ownerId: usr_ahfFktBBHUIxbVG5P source: api createdAt: '2025-10-28T00:40:37.917Z' createdBy: usr_ahfFktBBHUIxbVG5P fieldRejections: [] crmSync: provider: hubspot crmRecordId: '12345678901' syncDisabled: false errors: [] '400': description: >- Invalid request: `INVALID_COMPANY_ID` (the id is not a `cpn_xxx` id). content: application/json: example: success: false error: code: INVALID_COMPANY_ID message: Invalid companyId format '401': description: The authentication you supplied is incorrect. content: text/plain: example: The authentication you supplied is incorrect '404': description: No company of your team carries this id (`COMPANY_NOT_FOUND_BY_ID`). content: application/json: example: success: false error: code: COMPANY_NOT_FOUND_BY_ID message: No company found with id '405': description: Method not allowed. components: schemas: Company: type: object description: An organization record in your CRM. properties: _id: type: string description: Unique company identifier teamId: type: string description: >- Team the company belongs to. Returned by `GET /companies/{companyId}` and the `idsOrDomains` and `crmIds` lookups; the paginated list returns it only when requested with `fields`. domain: type: string description: Website domain linkedinUrl: type: string description: >- LinkedIn company page URL. Returned by `GET /companies/{companyId}` and the `idsOrDomains` and `crmIds` lookups; the paginated list returns it only when requested with `fields`. linkedinUrlSalesNav: type: string description: >- Sales Navigator company URL. Returned by `GET /companies/{companyId}` and the `idsOrDomains` and `crmIds` lookups; the paginated list returns it only when requested with `fields`. fields: type: object description: >- Key/value attributes of the company, standard and custom (e.g., name, picture, industry, location, size, foundedOn). These values are always under `fields`, never at the top level of the object. additionalProperties: true createdBy: type: string description: User ID who created the company ownerId: type: string description: User ID of the owner of the company createdAt: type: string format: date-time description: Creation timestamp source: type: string description: >- Origin of the company record, e.g. `api` when it was created through this API. Returned by `GET /companies/{companyId}` and the `idsOrDomains` and `crmIds` lookups, not by the paginated list. fieldRejections: type: array description: >- Values lemlist refused to write on this company, each with its reason. Empty when none. Filter the list endpoint to only flagged companies via `GET /companies?fieldRejectionReason=...`. items: $ref: '#/components/schemas/FieldRejection' crmSync: type: object nullable: true description: >- CRM sync status for the company, resolved against the team's active CRM provider (Hubspot, Salesforce, or Pipedrive). Only present when a CRM is connected. Use this block to monitor sync state and resolve duplicates (e.g. via `GET /companies?crmSyncStatus=unique_index_error_company`). properties: provider: type: string enum: - hubspot - salesforce - pipedrive description: Active CRM provider for the team. crmRecordId: type: string nullable: true description: >- Identifier of the company record on the CRM side. `null` when the lemlist company has not been synced yet. syncDisabled: type: boolean description: When `true`, automatic sync is paused for this company. errors: type: array description: >- List of recent sync errors. Empty when the company is synced cleanly. items: type: object properties: type: type: string description: >- Coarse error category (e.g. `CONNECT_FAILED`, `CREATE_FAILED`, `UPDATE_FAILED`). reason: type: string description: >- Specific error reason. Matches the lowercase form accepted by the `crmSyncStatus` query param (e.g. `UNIQUE_INDEX_ERROR_COMPANY`, `PROPERTY_DOESNT_EXIST`, `REQUIRED_FIELD_MISSING`). raisedAt: type: string format: date-time description: Timestamp when the error was last raised. metadata: type: object additionalProperties: true description: >- Extra context. For `UNIQUE_INDEX_ERROR_COMPANY`, contains `alreadyExistingCompanyId` — the lemlist company that already occupies the conflicting CRM record. Use it to remap contacts onto the right lemlist company before deleting the duplicate. FieldRejection: type: object description: >- A value lemlist refused to write on a Contact or Company, with the reason why. Surfaced under `fieldRejections[]` on those objects; filter a list endpoint to only flagged records via the `fieldRejectionReason` query param. properties: field: type: string description: >- The record field the rejected value targeted (e.g. `emails`, `linkedinUrl`, `domain`). reason: type: string description: >- Why the value was rejected, prefixed by its origin — `enrichment_*` (raised while enriching) or `crm_sync_*` (raised during CRM sync). Same values accepted by the `fieldRejectionReason` query param. source: type: string description: >- Where the rejection came from — an enrichment source (`lemrich`) or a CRM provider (`hubspot`, `salesforce`, `pipedrive`). conflictingRecordId: type: string description: >- The lemlist record that already holds the value, when the rejection identifies one — use it to merge or remap before resolving the duplicate. Always a lemlist id (`ctc_…` for a contact, `cpn_…` for a company), never a CRM record id. Omitted otherwise. rejectedValue: type: string description: The value that was refused. rejectedAt: type: string format: date-time description: When the rejection was recorded. securitySchemes: basicAuth: type: http scheme: basic ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.