...
With your API account created with and the proper credentials in place, the request below returns a JSON block including an “access_token” field. This token becomes the Bearer
token required in the Authorization
head for secured requests to the API. (Note: An API account is configured by the CCCTC during the implementation process.)
...
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Note: In the example above the token request is made using cURL however any preferred API tool can be used, such as Python, PowerShell, Ruby, Java, etc. |
...
Getting Your
...
Access Token Using Postman
Panel | ||
---|---|---|
| ||
Required: You must have Postman installed & configured with your API account credentials and authorized MIS code to continue with the steps below. See Recommended: Refer to/wiki/spaces/GLUEPD/pages/2851438610 > Configuring Your API Account OAuth Specifications to get started. |
...
your access token using Postman. |
Once Postman is installed and the Fraud Report Postman Collection files have been imported and configured with your API account credentials and MIS code(s) for the pilot and production environments, the turn-key process for generating and refreshing your API access token is as easy as obtained on the Fraud Report OAuth tab by clicking the “Send” button. The access token is generated and automatically stored as the Bearer
token in the Authorization
head for all secured API requests (submitting and querying fraud reports).
Step 1: In your Postman Workspace left sidebar, click on the Collections icon and expand button to display the Fraud Report collection.
Step 2: Click on the Fraud Report OAuth file which will to open in a the tab in your Workbench.
Step 3:
...