> ## 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 companies from your CRM. Use `idsOrDomains` to fetch specific companies by ID or domain in a single request (max 100), or omit it to get a paginated list of all companies.
# Get Many Companies
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.
;
};
## OpenAPI
````yaml get /companies
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:
/companies:
get:
tags:
- Companies
summary: Get Many Companies
parameters:
- name: idsOrDomains
in: query
required: false
description: >-
Comma-separated list of company IDs or domains to fetch. When
provided, returns only matching companies (no pagination). Each
value is classified as a company ID (e.g. `cpn_xxx`) or a domain
(e.g. `example.com`). URLs are normalized automatically (e.g.
`https://example.com/path` → `example.com`). Invalid values are
silently skipped. Maximum 100 values.
example: cpn_gG7PsmZFpEAnpMCHO,persana.ai
schema:
type: string
- name: offset
in: query
required: false
description: >-
Number of companies to skip for pagination. Defaults to 0. Ignored
when `idsOrDomains` is provided.
schema:
type: integer
minimum: 0
default: 0
- name: sortBy
in: query
required: false
description: >-
The field by which to sort. Currently, only 'createdAt' is
supported.
example: createdAt
schema:
type: string
enum:
- createdAt
- name: sortOrder
in: query
required: false
description: >-
The sort direction. Use 'desc' for descending order; any other value
(or omission) will sort in ascending order.
example: desc
schema:
type: string
enum:
- asc
- desc
- name: search
in: query
required: false
description: Search by company name (case insensitive)
example: lemlist
schema:
type: string
- name: fields
in: query
required: false
description: >-
Returns selected fields. Returns all fields if empty. Each field is
separated by a comma (e.g., '_id,fields.name,domain')
example: _id,fields.name,domain
schema:
type: string
- name: limit
in: query
required: false
description: 'Number of companies to retrieve. Default: 100. Maximum: 500'
example: '10'
schema:
type: integer
minimum: 1
maximum: 500
default: 100
- name: crmSyncStatus
in: query
required: false
description: >-
Filter companies by their CRM sync state against the team's active
CRM provider. Requires a CRM (Hubspot, Salesforce, or Pipedrive) to
be connected — otherwise the request returns `400 NO_CRM_CONNECTED`.
Common values:
- `synced` — the company has a CRM record and no sync errors.
- `not_synced` — the company has no CRM record yet.
- `error` — at least one sync error is currently raised.
- A specific error reason (lowercase form), to filter by root cause:
`unique_index_error_company`, `property_doesnt_exist`,
`required_field_missing`, `company_already_exists_with_name`,
`company_already_exists_with_linkedin_url`.
For each returned company, see
`crmSync.errors[].metadata.alreadyExistingCompanyId` to identify the
lemlist company that already occupies the conflicting CRM record
(useful to remap contacts before deleting the duplicate).
example: unique_index_error_company
schema:
type: string
enum:
- synced
- not_synced
- error
- unique_index_error_company
- property_doesnt_exist
- required_field_missing
- company_already_exists_with_name
- company_already_exists_with_linkedin_url
responses:
'200':
description: Success
content:
application/json:
schema:
type: object
properties:
data:
type: array
items:
$ref: '#/components/schemas/Company'
total:
type: integer
limit:
type: integer
offset:
type: integer
required:
- data
- total
- limit
- offset
example:
data:
- _id: cpn_gG7PsmZFpEAnpMCHO
createdAt: '2025-10-26T11:54:27.387Z'
createdBy: usr_iGBmhLaxZmL0s7k1G
domain: persana.ai
fields:
name: Persana AI
picture: https://example.com/logos/company-1.png
ownerId: usr_iGBmhLaxZmL0s7k1G
- _id: cpn_FEWCjzMWXo5StjpDa
createdAt: '2025-10-26T11:45:18.773Z'
createdBy: usr_iGBmhLaxZmL0s7k1G
domain: duno.ai
fields:
industry: IT Services and IT Consulting
name: Duno.ai
picture: https://example.com/logos/company-2.png
ownerId: usr_iGBmhLaxZmL0s7k1G
- _id: cpn_2STz8x5Bexmd0nvIz
createdAt: '2025-10-25T21:37:45.741Z'
createdBy: usr_iGBmhLaxZmL0s7k1G
domain: tally.so
fields:
industry: Computer Software
name: lemlist family
picture: https://example.com/logos/lemlist.png
ownerId: usr_iGBmhLaxZmL0s7k1G
- _id: cpn_Qf4CJuUrNUNmHm6uZ
createdAt: '2025-10-24T07:26:34.956Z'
createdBy: usr_ahfFktBBHUIxbVG5P
domain: example.com
fields:
name: Growth & GTM Engineering
ownerId: usr_ahfFktBBHUIxbVG5P
- _id: cpn_A1B2C3D4E5F6G7H8I
createdAt: '2025-11-02T09:14:08.512Z'
createdBy: usr_A1B2C3D4E5F6G7H8I
domain: acme.com
fields:
name: Acme Inc
ownerId: usr_A1B2C3D4E5F6G7H8I
crmSync:
provider: hubspot
crmRecordId: null
syncDisabled: false
errors:
- type: CONNECT_FAILED
reason: UNIQUE_INDEX_ERROR_COMPANY
raisedAt: '2025-11-02T09:14:12.034Z'
metadata:
alreadyExistingCompanyId: cpn_J1K2L3M4N5O6P7Q8R
total: 59310
limit: 100
offset: 0
'400':
description: Bad team
content:
text/plain:
example: Bad team
'401':
description: The authentication you supplied is incorrect
content:
text/plain:
example: The authentication you supplied is incorrect
'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
name:
type: string
description: Company name (may also be present under fields.name)
domain:
type: string
description: Website domain
industry:
type: string
description: Industry sector
size:
type: string
description: Company size
location:
type: string
description: Geographic location
fields:
type: object
description: >-
Flexible key/value fields of the company (e.g., name, picture,
industry, location, size, foundedOn)
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
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.
securitySchemes:
basicAuth:
type: http
scheme: basic
````