Category: QuickBooks API
-
Updates to the Payments APIs for QuickBooks Online may affect your application
Beginning February 1, 2018, the QuickBooks Online Payments API and QuickBooks Merchant Services Payments API will require that the ecommerce and mobile indicators for all purchases made from a handheld device (smartphone or tablet) to be set within the application.
-
Using QuickBooks Online API for automated sales tax
As of November 10, 2017, all new US QuickBooks Online companies manage sales tax calculations via an automated sales tax (AST) engine. Sales tax is computed automatically on the sales transaction based upon the shipping address and the location of the company rather assigning sales tax manually. Read more about how QuickBooks Online implements automated […]
-
Part 3: NodeJS Inventory Tracking Sample App
We’re back again with part 3 of the NodeJS Inventory Tracking Sample App. In this addition, we’ve included a reporting call and displayed it using plot.ly. Built on top of d3.js and stack.gl, plotly.js is a high-level, declarative charting library. Plotly.js ships with 20 chart types, including 3D charts, statistical graphs, and SVG maps.
-
Minor Versions: What are they and why they matter to you
At Intuit, we’re constantly improving our products including the QuickBooks Online API. This means we need to be able to introduce incremental changes to the API without breaking your app. Minor versions provides a way to do just that. Now, let’s look at how it works, so you can take advantage of new features today!
-
Upgrading your apps to support TLS 1.2
We recently announced that QuickBooks Online apps will be required to upgrade to TLS 1.1 or above by July 31, 2017 to align with industry best practices for security and data integrity. Intuit will also require an upgrade to TLS 1.2 by December 31, 2017. Steps for upgrading to TLS 1.2 vary for different coding languages.
-
Updates to the Payments APIs for QuickBooks Online
Beginning February 1, 2018, Intuit is making a change to the QuickBooks Online Payments API and QuickBooks Merchant Services Payments API that will require that the ecommerce and mobile indicators for all purchases made from a handheld device (smart phone or tablet) is set within the application. This will affect any purchase regardless if the card number is keyed in, swiped, or fetched from a pass through digital wallet like Apple Pay or a staged digital wallet like PayPal/Google Wallet.
-
OAuth 2.0/OpenID Connect now available for New Developers
Today we are happy to announce the general availability of OAuth 2.0 and OpenID Connect for new developers on the QuickBooks Online platform. As a new developer on the platform you will be able to implement OAuth 2.0 and OpenID Connect for authorization and authentication.
-
TLS 1.0 and 1.1 Disablement for the Intuit Developer Group
Intuit is requiring an upgrade to TLS 1.2 by July 30, 2017 in order to align with industry best practices for security and data integrity. On July 30, 2017, we will disable the TLS 1.0 & 1.1 encryption protocols, which will prevent apps still using them from accessing Intuit and QuickBooks APIs and Services.
-
Intuit is updating its OpenID IP addresses
Apps use IP whitelisting to ensure that they are communicating with Intuit securely. If your app uses IP whitelisting please note that the Intuit OpenID IP addresses are changing soon and you would need to update your systems to add the new IP addresses.
-
Reimburse charge support with QuickBooks Online API
We have had requests from multiple developers to expose details of ReimburseCharge (also known as Expense Charge or Billable Expense) linked transactions for Invoice objects. Our teams worked diligently on understanding the underlying data requirements and have provided read support for all details related to ReimburseCharge for Invoice objects starting with minorversion=9 or greater.