Your server-side app will use QuickBooks Online OAuth libraries or endpoints to implement the OAuth 2.0 authorization that allows your apps to access QuickBooks Online APIs. OAuth 2.0 lets an application access specified user data without requiring access to a user’s private credentials. This means that an application can use OAuth 2.0 to obtain permission from a QuickBooks Company admin to read and write data to their QuickBooks company.
This OAuth 2.0 flow is designed to allow your app to access the QuickBooks Online API whether the user is interacting with the application or not.
Code samples and SDKs
Here are some code samples and SDKs with client libraries that can help you implement OAuth 2.0.
OAuth 2.0 sample integrations included in SDKs:
Sample OAuth 2.0 implementations that are SDK independent:
To begin, get your OAuth keys from your app’s Keys and OAuth section under Development or Production. Your app uses these keys to get an access token from the Intuit OAuth service for access to the QuickBooks company for which the admin user authorizes.
|Keys||Client ID and Client Secret in your app’s Keys and OAuth section under Development or Production|
|URI to serve OAuth requests||Redirect URI in your app’s Keys and OAuth section under Development or Production|
|URI to serve Intuit Single Sign-0n requests||App URLs in your app’s Keys and OAuth section under Development or Production|
|Playground||OAuth 2.0 playground|
|Identity authentication||OpenID Connect|
|Documentation||OAuth 2.0 integration and OpenID Connect integration|
Here is an example of your app’s Client ID and Client Secret: