Within the body of the “Charge-Create” call, you see: "capture": "false" Using this token, we create a charge in the next API Cal, “Charge-Create”. In the “Tokens-Create” call, we enter in a credit card’s details, which creates a temporary token, which represents this Credit Card. Lets take a look at each API Call and see what it does. There are three API calls within this use case, “Tokens-Create”, “Charge-Create”, and “Charges-CaptureCharge”. Select “Create a credit card token, authorize a charge, and then capture the charge” under the QuickBooks Payments API Collection. In this tutorial, we will walk through “Create a credit card token, authorize a charge, and then capture the charge”.ġ. Now that we’ve imported the collection to your Postman, let’s take a look at one of the use cases in detail. In this use case, we will only be passing in the credit card details. For more information about the Token-Create API Call, please refer to its Reference. Select Body to take a look at the request body. You’ll see the request body of this call. Also note: the baseurl, companid, minorversion are all saved as environment variables here.Ĥ. Select “QBOV3-Payments-Env-Variables” and fill in the consumerKey, consumerSecret, OAuth AccessToken, OAuth AccessSecret, and the RealmId with your credentials. For information on where to get these, please check out Configure the Postman Authorization header. Go to the gear icon in the top right of Postman and select Manage Environments.ģ. At this point, you need to enter your App credentials. This is a POST call with the following URI the base URL for the Payments API is stored as an environment variable.Ģ. The API Call window opens up for “Tokens-Create”. Select the API call “Tokens-Create” from the Tokens folder. Now that we’ve imported the collection to your Postman, lets take a look at one of the API calls.ġ. Three of them are common Payments API use cases for which we have created orchestrations. This collection contains five folders that group API calls related to specific objects. A new collection, “QuickBooks Payments API Collections” will show up in your Postman App. Importing the Payments API Collections to the Postman AppĢ. With all that lets get started! The first thing to do is to import a collection to your Postman App. For more information about the Payments API’s, please refer to the API reference. In the same app, easily record transactions in QuickBooks Online. The QuickBooks Online Payments API is a RESTful API that is used to access QuickBooks companies. The Payments API allows you to process credit card payments on your eCommerce website or set up online processing for your customer’s site. This tutorial will help you quickly get started using Postman Runner with the QuickBooks Payments APIs. We’ve put together three such chains highlighting some of the most important use cases of QuickBooks Payments APIs. Using Postman Runner, a tool that chains together several API endpoints to create useful flows, you can easily see how effective a combination of several QuickBooks Online API calls can be. For more information about Postman collections, click here. We’re really happy to announce Postman collections and orchestrations for QuickBooks Payments API.Ī Postman collection lets you group individual requests together and interact with them without writing a single line of code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |