Postman instructions to test Aptean Food and Beverage APIs
This topic describes the setup and initialization of Postman and the corresponding work instructions to test the released Aptean Food and Beverage APIs on your Business Central environment.
Prerequisites
The latest version of Postman app can be downloaded here.
Postman account (free or Gmail) must be created.
Set up Workspace for Debugging and manual testing.
Team creation is not mandatory.
Get app registration information to be able to authenticate by using OAuth against your Business Central Online environment or create one as described in the Microsoft documentation.
ImportantSave the Client ID, Tenant ID and Secret for setup of the Postman environment variables as next steps.
Import and configure postman environment
Download the latest version of Postman Aptean BC Environment Variables here.
- Select Import and import the Aptean BC.postman_environment.json file.
Select the Aptean BC environment. Click the Environment quick look icon and then click Edit to set the current values for variables.
Set your Domain or TenantID and your Environment name to be used as current value for URL.
To be able to use the OAuth Authorization, set the earlier saved TenantID, ClientID and Secret of the application registration in the Postman Environment variables.
NoteFor all example requests, these will now be used as the default values to authorize by using OAuth.
Using the Get New Access Token button, the Bearer Token should become available to be used in your requests.
Import postman requests collection
- Download the latest version of Postman Aptean Labeling Requests Collection here.
- Import again and import the Aptean Labeling.postman_collection.json file. Open Collections to find all provided requests.
- Initialize your environment variables by running the GET Requests.
- Initialize Companies Environment Variables
ImportantMake sure to get a (new) Bearer Token for authentication as described in the previous steps to be able to send requests.
- Now it is possible to test all provided requests and see the response messages.
ImportantWhen a POST request is sent, the body of the message should contain the correct data (the record to print should be available and a label setup should be present) before proceeding with your tests.