The OAuth 2.0 playground is a tool used to experiment with the OAuth 2.0 protocol and QuickBooks Online APIs. It is pre-configured to use with Intuit's OAuth 2.0 endpoints so you can quickly get started. The playground allows you to walk through each step in both the OAuth 2.0 and OpenID Connect workflows in order to understand how these protocols work. At each step the playground displays the full HTTP request and response.
Looking for the OAuth 1 playground? Click here.
Invoke the OAuth 2.0 playground for your app.
The OAuth 2.0 Playground appears pre-populated with your app's development Client ID and Client Secret. If you want to use production keys instead, select the production app from the drop-down list.
Now, authorize the connection between your app and the QuickBooks company. The playground uses its own OAuth redirect URI to field the authorization request;
From here, use the playground to make API calls or refresh the access token.
The Make API Calls panel is populated with the realm Id (labeled Company ID) and the current access token, ready for you to test out some API calls. The Call API dropdown list contains the three available API calls you can make from the playground. Availability of each is based on the scopes you choose when getting your access token.
|API call||Required scope||Description|
|Get Company Info||com.intuit.quickbooks.accounting||Calls the QuickBooks Online API CompanyInfo resource to get information about the company corresponding to the realm Id.|
|Submit Charge||com.intuit.quickbooks.payments||Calls the QuickBooks Payments API Charges resource to create a charge to the test Visa card account.|
|Get User Info||OpenID and at least one of Profile, Email, Phone, Address.||Calls the userinfo resource to get additional information about the logged in user. The information retured is based on OpenID scopes chosen during authorization.|
The Refresh Access Token panel is populated with the current access and refresh tokens. Click Refresh Access Token to refresh the token. As a general rule, access tokens need to be refreshed every 60 minutes. Click here for further information about refreshing access tokens.
Got Questions? Get Answers in our developer forums.