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 as GET /api/contacts/{idOrEmail} for contacts.

  • Contact notes: GET /api/contacts/{idOrEmail}/notes lists a contact's notes, POST /api/contacts/{idOrEmail}/notes adds 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, and POST /api/companies/lists/{listId}/entities (add companies, or remove with ?action=remove), mirroring the contact list endpoints.

  • Find by CRM id: crmIds on GET /api/contacts and GET /api/companies looks 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 the search_contacts and search_companies tools.

  • Every contact returned by a lookup now includes a crmSync block (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}/notes and 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 crmId parameter was removed from both reads; use crmIds instead.

  • GET /api/companies/{companyId} only accepts the lemlist id (cpn_…). To find a company by domain, use GET /api/companies?idsOrDomains=.

  • A lookup with idsOrEmails that matches nothing still returns a 404, while idsOrDomains and crmIds return an empty list. This difference is intentional and stays as is.