Last updated

QUICK START

Pre-requisites

Authentication:

All API calls require a Bearer token passed in the header.

The token is valid for 1 hour. For continued access, reauthenticate (for testing) or implement a refresh token mechanism (for production).

Authenticate process is detailed below.


Getting Started

Download API Definition:

Each API definition can be downloaded in either YAML or JSON format from the link at the top.

Each API definition will have its own download for that product.

Styled imageStyled image

Choose A Path To Test the API

Options for Testing
API Testing Environment
In Portal Testing
Postman
Bruno
Other Service

API Testing Environment Path

  1. Choose an API Testing Environment
    • Examples of these are:
      • Postman
      • Bruno
  2. Import the API Definition

There is No Limitation to These: You can use other API testing tools as well.

Authentication:

In Postman:

  • Set the base URL to the server name.
  • Create a script to update the token variable for subsequent endpoint calls.
  • Set the authentication to following endpoint to 'Inherit from Parent'

    Postman Documentation

    In Bruno:
  • Set the base URL to the server name
  • Create a script to update the token variable for subsequent endpoint calls:
    • In the collection settings, go to the “Auth” tab.
    • Choose the appropriate authentication method (e.g., OAuth 2.0, Bearer Token).
    • Configure the authentication details and set up a script to update the token variable. You can use the Pre-request Script tab to write a script that fetches and updates the token2.
  • Set the authentication to ‘Inherit from Parent’:
    • For each request in your collection, go to the request settings.
    • In the “Auth” tab, select “Inherit from collection” to use the authentication settings from the collection level2.

      Bruno Documentation

Testing of the API in the Portal

Testing in Browser:

The Authenticate process will be identical for each API Product.

Information

This example uses the Sandbox Environment


STEP 1

Acquire Authenticate Token

  • Select Authenticate Endpoint
  • Click the "Try it" button to test endpoints directly on-screen.
Styled imageStyled image
  • Select Environment in the top right hand corner
  • Enter username and password in the requestBody
  • Submit request
  • Copy the returned token
Styled imageStyled image

STEP 2

Create Authenticate Variable

  • Select the Endpoint required
  • Reselect Try it button
  • Click the Security Tab
  • Set the Authorization type to 'JWT'
  • Complete the numbered steps below:
Styled imageStyled image

Point 1:

  • In the Environments tab, under the Sandbox the authenticate variable should be automatically created.

If the variable does exist move, to points 2 and 3 if not;

  • Select ' + New variable '

Point 2 & 3:

  • Edit Variable information:
    • Name: 'bearerToken_token' [This should be pre-populated by the security schema]
    • Value: ' Paste the Bearer token from the Authenticate Endpoint '
  • Save the Variable

Point 4:

  • The variable name should be pre-populated in the field {{variableName}}
    If the variable was created successfully it will appear in the list of selectable names

API Documentation and Resources

Location:

All API documentation and resources can be found on the sidebar.

All endpoints are detailed in the API documentation section.

Error Responses
Descriptions:

Detailed descriptions of what has happened are provided in the Error Responses.

Companies may handle errors differently based on their own policies.

By following these steps, you can quickly get started with integrating and testing the API. For more detailed instructions and examples, refer to the comprehensive API documentation.