and global markets.īeginning March 1, 2015, only existing app customers will be able to connect to QuickBooks Desktop through the QuickBooks Desktop REST API. The updated API eliminates connection fees, simplifies third-party collaboration, and offers developers the opportunity to build applications that integrate across U.S. This includes the decision to prioritize our developer resources on the QuickBooks Online APIs. As a result, we are re-focusing our energy and resources. In fact, we’ve reached an inflection point where more new users are choosing QuickBooks Online than QuickBooks Desktop. We are in the midst of a platform shift from desktop to QuickBooks Online. If you have specific questions, please don’t hesitate to open a support ticket with us or contact your partner manager directly. 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.Once migrated to QuickBooks Online, they can reconnect your application with their data. Your customers can call the QuickBooks migration hotline at 1-80 to discuss their migration options with an expert. Encourage your existing desktop customers to migrate to QuickBooks Online.If you have not already done so, build an integration with QuickBooks Online and publish it on.To help make this transition as painless as possible, we recommend the following: We encourage developers to transition, when you are ready, to QuickBooks Online.
We believe that the QuickBooks Online ecosystem offers developers and customers many benefits of a full SaaS solution. We understand that this transition may not be easy for some developers.
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. Admin Timeline to Discontinue the QuickBooks Desktop REST API