136 named actions covering clients, orders, services, invoices, transactions, quotes, tickets, products, projects and administration. It is the supported way to integrate; writing to the database directly is not.
- Every response has a result field. Check it first: a response with data in it can still be a failure.
- Do not judge success by the HTTP status alone.
- Expect new fields over time; read the ones you need.
- Client sign-ins through the API count towards the same limits as the sign-in page.
- Every request is logged with its action and outcome.
Poll at the speed the data changes
The API runs against the same database as your website. React to a hook instead of asking every few seconds for something that changes daily.
Full guide
The complete reference is API reference in the WBAMS documentation.