Contacts and Companies API reach feature parity
The Contacts and Companies endpoints now support the same actions, with the same behavior, and all of it is documented in the public API reference.
Read one company by its id:
GET /api/companies/{companyId}returns the company, or a 404 if it doesn't exist in the team — same asGET /api/contacts/{idOrEmail}for contacts.Contact notes:
GET /api/contacts/{idOrEmail}/noteslists a contact's notes,POST /api/contacts/{idOrEmail}/notesadds one. A note created over the API shows up in lemlist, syncs to the connected CRM, and is authored by the user of the API key — the same contract as company notes.Company lists:
GET /api/companies/lists,POST /api/companies/lists, andPOST /api/companies/lists/{listId}/entities(add companies, or remove with?action=remove), mirroring the contact list endpoints.Find by CRM id:
crmIdsonGET /api/contactsandGET /api/companieslooks up contacts or companies by their HubSpot, Salesforce, or Pipedrive record id, up to 100 at once. This is now documented and also available to AI agents through thesearch_contactsandsearch_companiestools.Every contact returned by a lookup now includes a
crmSyncblock (CRM, record id, sync errors), matching what companies already return.
This is available to every team with API access, with no change in the app UI.
A few related changes:
POST /api/companies/{companyId}/notesand the new contact notes endpoint now reject notes containing<or>, and notes over 10,000 characters, with a 400 and an explicit message.The single-value
crmIdparameter was removed from both reads; usecrmIdsinstead.GET /api/companies/{companyId}only accepts the lemlist id (cpn_…). To find a company by domain, useGET /api/companies?idsOrDomains=.A lookup with
idsOrEmailsthat matches nothing still returns a 404, whileidsOrDomainsandcrmIdsreturn an empty list. This difference is intentional and stays as is.