What the API does not cover
Eight modules of the CRM have no API surface at all. Knowing that in ten seconds is worth more than an afternoon spent looking for an endpoint that was never written.
No dates here. When one of these ships it will appear in the reference, and this page will get shorter.
| Module | What exists in the CRM | What you can do from the API meanwhile |
|---|---|---|
| Tasks | Assigning, due dates, reminders | Nothing. A note on the contact is the closest thing, and it is not one either. |
| Meetings and calendar | Public booking pages, availability, reminders, Google Calendar sync | Nothing. The booking page is public and needs no integration. |
| Follow-ups | Saved sequences that send on their own | Nothing. Send your own messages through the conversation endpoints. |
| Chatbot | Lead-capture flows on your site | Nothing here. The widget has its own endpoints, protected by a domain allow-list and not by a token — they are not integrator API and are deliberately out of this reference. |
| Help centre | Public articles, categories, search | Nothing. The centre is already a public website; read it over HTTP like anybody else. |
| Products | Catalogue, categories, prices | Nothing — and you do not need it: a quote carries its own items, with name, quantity and unit price. |
| Lead scoring | Rules, scores per contact | Nothing. The score is computed inside the CRM and is not readable from here. |
| Notes | Internal notes on a contact | Nothing. interest on a captured lead records what the person asked for, in their words. |
What is worth doing instead
Three things cover most of what people come here looking for:
- Subscribe to what happens. Outbound webhooks cover contacts, messages, deals, quotes and payments. If you were about to poll something, subscribe to it instead.
- Export the bulk reads. Exports hand you a filtered file instead of ten thousand pages of a list.
- Keep your own identifiers.
external_refon companies, deals, quotes and payments means you never store ours, and never have to reconcile two id spaces. See Two-way sales integration.
Something is here but not documented
Then it is a mistake in the documentation, not a boundary. The reference is generated from the routes and a test fails if an endpoint has no title or no description, so a gap is a bug — tell us and it gets fixed.