Timeline to Discontinue the QuickBooks Desktop REST API

UPDATED: February 3, 2015
Updated: October 6, 2014
Published: September 8, 2014

We want to share with you, our developer community, an important update about how Intuit will be prioritizing developer and platform resources in the coming years, with specific implications for the QuickBooks Desktop REST API.

The emergence of the cloud means that now, more than ever, we are serving customers on two distinct platforms – a desktop product and an online offering.

We’ve recently reached an inflection point where we now have more new users choosing QuickBooks Online than QuickBooks Desktop. Our customers are choosing QuickBooks Online because it helps them streamline operations, makes it possible to unlock a wealth of data-driven insights, and makes it easier than ever to reach new customers and partners around the world.

As a result of this market shift, we are re-focusing `our energy and resources on the QuickBooks Online APIs. In November 2013, we announced that we would no longer be onboarding new developers to the QuickBooks Desktop REST API. Today, we want to share with you the next steps and the plans to eventually discontinue service to the QuickBooks Desktop REST API – both v2 and v3. Here’s what this means for developers:

  • Beginning March 1, 2015, only existing app customers will be able to connect to QuickBooks Desktop through the QuickBooks Desktop REST API. 
  • Around September 2015, we will stop promoting QuickBooks Desktop REST API-based applications. This includes apps.com and in-product discovery in QuickBooks for Windows.
  • Beginning March 1, 2016, we will be discontinuing service of the QuickBooks Desktop REST API, both v2 and v3, and the Sync Manager service. 
  • Through March 1, 2016, we will continue to fix critical bugs with the QuickBooks Desktop REST API service as well as provide Sync Manager support.

We understand that this transition may not be easy for some developers.  We believe that the QuickBooks Online ecosystem offers developers and customers many benefits of a full SaaS solution. We encourage developers to transition, when you are ready, to QuickBooks Online.

To help make this transition as painless as possible, we recommend the following:

  1. If you have not already done so, build an integration with QuickBooks Online and publish it on apps.com.
  2. Encourage your existing desktop customers to migrate to QuickBooks Online. Your customers can call the QuickBooks migration hotline at 1-800-488-7330 to discuss their migration options with an expert. Once migrated to QuickBooks Online, they can reconnect your application with their data.
  3. For developers who want to continue building a QuickBooks Desktop integration, we ask that you use the QuickBooks Desktop SDK and the QuickBooks Web Connector.

If you have specific questions, please don’t hesitate to open a support ticket with us or contact your partner manager directly.


Why are you making this change now?

We are in the midst of a platform shift from desktop to QuickBooks Online. In fact, we’ve reached an inflection point where more new users are choosing QuickBooks Online than QuickBooks Desktop. As a result, we are re-focusing our energy and resources. This includes the decision to prioritize our developer resources on the QuickBooks Online APIs. The updated API eliminates connection fees, simplifies third-party collaboration, and offers developers the opportunity to build applications that integrate across U.S. and global markets.

What will happen on March 1, 2015?

Beginning March 1, 2015, only existing app customers will be able to connect to QuickBooks Desktop through the QuickBooks Desktop REST API. 

There is no specific action happening on March 1, 2015. We will continue to fix critical bugs with the QuickBooks Desktop REST API service, as well as provide Sync Manager support, until March 1, 2016.

What will happen after March 1, 2016?

Beginning March 1, 2016, we will discontinue service of the QuickBooks Desktop REST API and the Sync Manager service. 

If you haven’t already done so, we encourage you to build an integration with QuickBooks Online and publish it on apps.com.

If you want to maintain a QuickBooks Desktop integration, you will need to build a new integration using the QuickBooks Desktop SDK and the Intuit Web Connector.

FAQ ADDITIONS, 10/6/2014

Will Sync Manager be replaced by another applications? 

No. There are no plans to replace the Sync Manager.

Can we provide the customer-facing communications to developers beforehand?

Yes, we will keep developers informed on sync manager communications. Because the impact will vary from app to app, it’s important that app developers build their own customer-facing communications as well.

How does this affect the connection charges?

There is no impact to the connection charges.

What is the future of QuickBooks Desktop versus QuickBooks Online?

Intuit remains committed to both products, recognizing that new customers prefer QuickBooks Online. At its annual Investor Day on Sept. 30, 2014, Intuit reaffirmed its “strategic decisions to invest in the acceleration to cloud-based subscriptions and to improve the company’s future desktop offerings to encourage migration to online services.”







5 responses to “Timeline to Discontinue the QuickBooks Desktop REST API”

  1. trial1 Avatar

    The irony of this post appearing less than two weeks after the post entitled “Why ‘Partner’ is such an important word” is sickening… yet typical of the type of “partner” Intuit is.

    Responding to market shifts and demands is part of business. However, that response can and should be done in a thoughtful and responsible manner. While it is understandable that Intuit might decide not to build out the QBD IPP according to the original vision, it is irresponsible and bad partnership to sunset a technology that as recently as 12 months ago Intuit was insisting developers use when integrating to QBD. Developer “partners” have invested thousands upon thousands of man-hours developing applications based on Intuit’s insistence and commitments. Now is when these developer “partners” expect to recupe their investment, and hopefully to make a return on that investment. Pulling the rug out from underneath their “partners” (yet again) is just plain wrong.

    There are many apps running in production on the QBD IPP, with developer and customer “partners” relying on them. Intuit has a fiduciary responsibility to provide a stable and functioning platform for their development and customer “partners”… as well as to protect Intuit’s own reputation. It is irresponsible and bad partnership for Intuit to abandon support of that platform so soon.

    When an existing QBD customer decides to move to the cloud, they will investigate options (Xero, Freshbooks, QBO, etc). To the extent that a QBD customer is using IPP apps, the likelihood increases that that customer will move to QBO instead of a competitive product. It is short-sighted to shut off new QBD IPP app users in 6 months, and existing QBD IPP app users in 18 months. Give the cloud time to build the functionality that QBD users need… those functions simply aren’t there yet for whloesale distributors and manufacturers… and once they are there, it will take some time for QBD users to research and make the transition. Meanwhile, Intuit should continue support of the QBD IPP and demonstrate that they value their QBD customer and developer “partners” so they make the transition to the cloud with Intuit. Don’t cut off new QBD IPP app users at all. And extend the support period for QBD IPP and sync manager to 48 months. That is a reasonable amount of time to expect QBD users to be able to move to the cloud.

    This announcement — as well as the numerous commitments made and reneged on over even just the past 10 months (not to mention the past 4 years) — smacks of desperation and appears to be a knee-jerk reaction to competitive pressures rather than a well-considered and smooth re-direction. This is just one more example of Intuit leaving their “partners” bloodied and raising serious questions about the value of Intuit as a partner, not to mention Intuit management’s acumen. Come on Intuit… put your money where your mouth is and show your customer and developer “partners” “Why ‘Partner” is such as important word.”

  2. Stephanie Allemann Avatar

    I realized I was logged in under the wrong username when I posted the previous comment. For clarity, I posted the comment. I can be reached at steph [at-sign] crik-it.com.

  3. Joe Dwyer Avatar

    Hi Steph,

    I can sympathize with you on this. I know that all involved, especially Intuit, sees the trouble they’ve had with their sync manager and attempts to make QuickBooks desktop sync fully to the cloud.

    As a long time QuickBooks developer, we’ve built dozens of integrations for people using the desktop SDK and IPP. Having to change directions back to enabling the desktop SDK can be a bit of work for people who invested in IPP for QBD. Fortunately, their support of the desktop SDK has not waivered over the years and has lots of capabilities within it. As an integrator, we’ve also taken a bunch of steps to ensure QBD connects really well with cloud apps. The sync manager from Intuit just didn’t get great traction.

    Considering Intuit as a partner, I’m on the opposite end of your comments. Of all the companies we work with to connect data to QuickBooks, Intuit is BY FAR the easiest to work with. They have super easy access to the whole developer relations team. Their marketing team is super helpful. And, they are way in favor of helping to make a successful ecosystem. A small example of this is an 18 month sunset period for the sync manager. That’s way longer than the vast majority of companies would support a struggling technology.

    As for next steps, the desktop SDK is great. Our Autofy system has connected to it for over a decade and it’s super solid. We connect it to on-premise and cloud apps. So, it’s a good choice for QuickBooks desktop integration.

  4. Stephanie Allemann Avatar
    Stephanie Allemann

    Update:As mentioned above, Intuit is discontinuing the QuickBooks sync manager. Because we have many QuickBooks Desktop users relying on our Crik-IT B2B Portal and CRM app, we have written our own sync manager, called Crik-IT Sync Manager (CISM). If there are any developers out there looking for a replacement for the QuickBooks sync manager, feel free to contact us to learn more about CISM and whether it might work for your application. Call us at 207- 956-0685 or email us at info [at sign] crik-it.com.Notes:CISM offers REST and SOAP interfaces.CISM does not use Intuit’s Web Connector. Why not:1) We have had feedback from several developers that the Web Connector has significant performance issues, especially noticeable in high volume applications. The underlying design of the Web Connector is the cause of the performance issues.2) Having worked as an Intuit Development “Partner” over the past several years, we have seen Intuit change direction many, many times. These reversals result in developers having to scramble to retrofit their apps according to Intuit’s latest dictates, investing thousands of hours and tens of thousands of dollars to reinvent the wheel. To reduce exposure to future Intuit direction changes, we are using as few Intuit tools as possible to accomplish our goals.

  5. Claire Milligan Avatar
    Claire Milligan

    If you’re a QuickBooks developer concerned about Sync Manager and are looking for a replacement, SpringAhead recommends that you take a look at AccountingSync. You can find them at AccountingSync.com. Feel free to send me a message if you’re interested in speaking with the sales team!

Leave a Reply

Your email address will not be published. Required fields are marked *