QuickBooks Online is increasingly not a choice, it's where Intuit is pushing every QuickBooks user, and its API reflects that it was built as an accounting system first. This covers what's actually happening with QuickBooks Desktop's shrinking support window, the real constraints QBO's API puts on any integration built against it, and how InfiPlex connects to it.
Jump to What You Need
| If You Want To… | Jump To |
|---|---|
| Understand what's actually happening to QuickBooks Desktop | The Desktop Sunset, With Real Dates |
| See QBO's real API limits, not marketing language | What QBO's API Actually Restricts |
| Understand why webhooks alone aren't enough | Why Webhooks Don't Solve This by Themselves |
| See how InfiPlex actually connects to QBO | How InfiPlex Connects to QuickBooks Online |
The QuickBooks Desktop Sunset, With Real Dates
Intuit stopped selling new Pro Plus, Premier Plus, and Mac Plus subscriptions in September 2024. Desktop 2024 is confirmed as the final release of those product lines, there will be no 2025, 2026, or 2027 version. Support then rolls off on a fixed three-year schedule per version: Desktop 2022 lost support in May 2025, and Desktop 2023's support window closed on May 31, 2026. Desktop 2024 carries support through September 30, 2027, after which nothing is left except QuickBooks Desktop Enterprise, which Intuit has explicitly carved out and continues to sell and support with no announced end date.
When a version's support window closes, the software still opens, but bank feeds, payroll, payment processing, and security updates all stop. Pricing has also continued to rise on the versions still being sold; Pro Plus increased from $999 to $1,149 in February 2026 alone.
None of this means Desktop disappears overnight. It means the path is narrowing on a fixed schedule, and QuickBooks Online is where Intuit is actively moving its installed base, not a parallel option Intuit is maintaining indefinitely for non-Enterprise users.
What Does QBO's API Actually Restrict?
QuickBooks Online's API is built around its accounting data model first, and several of its real constraints come directly from that.
| Constraint | What it means |
|---|---|
| Rate limit | 500 requests per minute per company. Exceeding it returns a 429 error. |
| Access token expiry | Access tokens expire every hour and must be refreshed. |
| Refresh token expiry | The refresh token itself expires after 100 days and rotates on every use, the previous one is invalidated each time. An integration that doesn't handle this correctly can lose its connection silently. |
| Pagination | Offset-based, not cursor-based. Since an accounting ledger changes constantly, records can be missed or duplicated if data shifts mid-fetch unless queries are ordered carefully by last-updated time. |
| Desktop compatibility | None. QuickBooks Desktop uses an entirely separate integration method (Web Connector or the Desktop SDK, both XML-based), incompatible with the Online API. |
Why Don't Webhooks Solve This by Themselves?
QuickBooks Online does offer webhooks, but they carry a real limitation: a webhook event typically tells you that something changed, not what changed. Getting the actual updated record still requires a separate API call, and delivery isn't instant. Because of this, a webhook-only design still needs a polling layer behind it to catch anything missed or delayed, which is why many integrations end up building both anyway rather than replacing one with the other.
How Does InfiPlex Connect to QuickBooks Online?
InfiPlex connects to QuickBooks Online through scheduled polling rather than a webhook listener. Given that a webhook alone still requires a follow-up API call to get the full record, a well-tuned polling cycle reaches the same complete data directly, without the added layer of maintaining a separate webhook endpoint and reconciling it against what polling already covers. Orders sync from every connected channel into QuickBooks as sales, while the InfiPlex OMS holds the real-time inventory count and pushes accurate quantities back, roughly every 15 minutes.
On the refresh-token risk specifically: InfiPlex's connection to QuickBooks Online is built to survive long gaps, well past the 100-day refresh token window, without requiring a manual reconnection. That's not automatic for every integration; it's a specific, deliberate part of how the connection is built, since a refresh token that isn't handled correctly is a documented, real way integrations go quiet without anyone noticing until something doesn't sync.
See the InfiPlex QuickBooks Online integration | See the step-by-step setup guide | Get a free demo
QuickBooks Online Integration Questions
Is QuickBooks Desktop actually being discontinued?
Not overnight, but the path is narrowing on a fixed schedule. No new Pro Plus, Premier Plus, or Mac Plus subscriptions have been sold since September 2024, Desktop 2024 is the final version of those lines, and each version loses support three years after release. QuickBooks Desktop Enterprise is the one exception Intuit continues to sell and support without an announced end date.
What happens when a QuickBooks Desktop version's support ends?
The software still opens, but bank feeds, payroll, payment processing, and security updates stop working entirely.
What are QuickBooks Online's actual API rate limits?
500 requests per minute per company. Exceeding it returns a 429 error, requiring the request to be retried after a delay.
Why would a QuickBooks Online integration lose its connection unexpectedly?
The most common cause is the refresh token. It expires after 100 days and rotates every time it's used, so an integration that doesn't manage that rotation correctly can lose access without any obvious warning.
Do QuickBooks Online webhooks provide real-time data by themselves?
Not completely. A webhook typically signals that a record changed without including the full details, so a separate API call is still needed to retrieve them, and many integrations pair webhooks with polling rather than relying on webhooks alone.
Does InfiPlex's QuickBooks Online connection require reconnecting periodically?
No. It's built to handle the refresh token's 100-day expiry and rotation automatically, without manual reconnection.
Need Something This Doesn't Cover?
Contact Us and we'll take a look. Support is included with every InfiPlex plan.
