Skip to main content
The API lets another system read and change the same records you work with in the product: sites, assets, work requests and work orders, meters, stock and the rest. This page says where to start.

Where to start

Integration API, below the guides, lists the calls those pages use, about fifty of them, grouped by what they are for. The Complete API tab lists every endpoint the application uses, about two thousand. Look there when the integration API does not have what you need. Most of those endpoints exist for one screen.

What this describes

Every screen in the application is a client of this API. There is no separate integration surface: the work orders you see in the product are the rows /work_orders returns, and creating one from the API runs the same function, under the same permissions, with the same audit trail as pressing the button. That has two consequences worth understanding before you read further. Your permissions apply. A token carries the roles and site access of the account it was issued to. An endpoint you can reach still leaves out the rows that account cannot see, and refuses the writes its permissions do not allow. Nothing here is a way around the product’s own rules. Your organisation’s set-up applies. Statuses, required fields, approval steps and rules are configured per organisation, and the API meets them exactly as the screens do. A request that succeeds for one organisation can be refused for another, with a message saying why.

How requests are shaped

Reads are lists — filter, sort and page them with query parameters, as Reading and filtering shows. Writes are actions under /rpc/, called with POST and a JSON body, each doing one thing completely. Every example on these pages uses https://app.assetinfinity.ai/api. A tenant on its own hostname uses that hostname instead.

Where the descriptions come from

Each endpoint’s description is written against the database object it is generated from, so it describes what that endpoint actually does rather than what a specification hoped it would. In the complete reference, some have no summary yet — those are endpoints whose underlying object has not been documented, not endpoints that do nothing. The shape shown is still generated from the real schema and is accurate.