API Specs - Update the environment in the Postman Collection to use the sandbox

[eason-pan-bc]

As we are delivering the API specs and the Postman Collections to clients, we need to change the environment used in the Postman collection from Dev to Sandbox.

References from PPR's Postman collection: https://developer.bcregistry.daxiom.ca/apigw-ppr-demo.postman_collection.json

Double-check the url for Business API Sandbox with Argus.

This ticket blocks the last step for the API specs publishing

TODOs:

• [x] Change the current Postman collection environment variable to use the Sandbox
• [x] Add necessary notes in the Postman collection to help clients understand the collections

[eason-pan-bc]

As per discussion, updated the Postman collection for the use of Sandbox, and clients using account_id and api-key.

Changes Made:

• As per discussion with Argus, removed 'setup' folder for retrieving a token and also the Authorization: Bearer header, which we used for the DEV environment.

  

• Updated Notes

  

• Changed the gateway_url to use the sandbox

  

• Reorganized the Sandbox environment, so users can easily find the place they can fill in their account info.

  

[eason-pan-bc]

adjusted x-apikey and Account-Id for each request

[eason-pan-bc]

Notes for QA:

• The updated version is in the shared Postman workspace. The collection is called Business API Demo
• Please select lear-api(Sandbox) environment to test it.
• You can find detailed instruction of how to run them in the overview of the collection.
• You will need an Api-key and account-id for using the Sandbox, please connect with Argus to borrow one.

• You will need to look at the Sandbox database, to find a business that exists in the db, and change the business identifier in the requests parameter

  and the business in th payload

[vishnup0422]

Received creds from Argus and was able to hit the endpoints on Sandbox env.