Integration notes by module
The generated module references list every route a module’s controllers serve. These pages answer the questions a route table cannot: which document types a module produces, which endpoint family a given screen calls, and — most often the one that bites — which rule the screen applies in the browser that the backend does not apply to a document you post directly.
Each page used to live under its module in the Modules section, and its old address still leads here.
Why claim endpoints do not look like the generic document endpoints
The contact-centre, lead, engagement and calendar endpoint families
Where the e-invoice endpoints are documented, and why the API does not make submission faster
Document types, the families a storefront or marketplace touches, and what the API will not do
Employee endpoints, and HR families that exist without a registered applet
Why reading a balance is not the same as reading availability
The two document types and the endpoint families an integration touches
The cash bill, and the till rule an integration must apply itself
Document types, how knock-off looks from outside, and what to respect
The sales document types, and the validations that are browser-only
The endpoint families, and six member and points endpoints documented one by one
Last updated on