One API pattern
Every operation is available at /api/{module}/{operation}, returning JSON, XML, CSV, or HTML — the same pattern across the platform, with record-scoped routes for working within a parent.
Cookies
We’d like to use analytics and advertising cookies to understand how the site is used and which ads bring visitors here. They stay off unless you allow them. See our privacy policy.
QBO Platform · Workflow APIs & integrations
QBO sits above your systems of record: one API pattern across every module, queues for long-running work, and plugin integrations for storage, messaging, AI, and data providers.
What it does
Every operation is available at /api/{module}/{operation}, returning JSON, XML, CSV, or HTML — the same pattern across the platform, with record-scoped routes for working within a parent.
Queued operations hand work to app servers through SQL Server Service Broker or Amazon SQS, so the web tier stays fast while large jobs run in the background.
Storage, generators, messaging providers, AI models, import engines, and external services (SQL, REST APIs) are plugins configured per installation, with configuration that can be overridden from the database.
Send orders to outside vendors through one API, receive their callbacks and referrals, and notify your systems by webhook when a transaction completes, with retries handled for you.
Extranet security applies to the API exactly as it does on screen, so you can open QBO to partners’ systems with confidence.
Core libraries target .NET Standard 2.0; the current platform runs on .NET 8 and later, in the cloud or on your infrastructure.
Building blocks
| API | Every operation at /api/{module}/{operation}, with record-scoped routes |
| Queuing | Long-running work at /api/{module}/queue/{operation}, run by app servers |
| Plugins & configuration | Storage, messaging, AI, import, and service plugins, configured per installation |
Integrations
More of the platform