Headers

Supplemental Data

Authorization

To allow secure data transmission between Suppliers and Distributors all API requests require HTTPS.

The API Key Token information for the staging and production environment will be sent in a separate mail.

If the request lacks any authentication information (e.g., the client was unaware that authentication is necessary or attempted using an unsupported authentication method), the resource server should not include an error code or other error information.

Authorization: Bearer JWT Token

---

Content-Type

The Content-Type should be application/json.

---

Accept-Encoding

This API is equipped to support gzip compression. By including "gzip" in the Accept-Encoding header parameter of your request, the API will reply with a compressed response using gzip format.

---

Application Info

Application info consists of data elements that identify the software that you use for making requests to the Prio platform. When you include application info in your requests, we can analyze and troubleshoot more efficiently, and provide a better support experience.

Application info includes:

• App-Name - Name of your application.

• App-Version - Version of your application.

• App-Flavor - Flavor of your application.

• App-Package-Name - Package name of your application.

• App-Build-Number - Build number of your application.

• App-Platform - Platform of your application (e.g Web, iOS, Android).

• App-Flavor - Flavor of your application.

• App-Reference - Unique request reference from your application.

• App-Machine-ID - Identifier of your machine.

Above values can be sent in the headers of any request and we recommend sending them if you have multiple applications directly interacting with this API. Custom headers can be sent as well, as long as they have the "App-" prefix attached.