HTTP Headers

Required API Headers

Include the following headers in every request. They ensure only authorized users access the correct resources.

Authorization – Bearer Token

Bearer Authentication (also known as Token Authentication) is required to access protected API endpoints that are not open to the public.

How it works

The server reads the token from the Authorization header.

It verifies the user’s permission to access the requested resource.

If the token is valid, the request will be processed; otherwise, access will be denied.

Important Security Notice
An access token does not grant universal access.
Each token only permits access to resources that belong to the authenticated user.
Any attempt to access unauthorized resources will be rejected.

Example:

Keep your token valid and refresh it when needed.

X-Partner-ID – Partner Identification

Every API partner must include a Partner ID in each request.

Why It Matters

The Partner uniquely links your system to the API service.

Without it, the API cannot identify the requesting partner and your request will be rejected.

How to Get a Partner ID

Contact the official API support team to obtain a registered Partner ID.

Include this header:

Ensure this header is included in every API request to avoid any issues!

Final Checklist

Every API request must include:

Authorization → A valid access token.

X-Partner-ID → A registered partner identifier.

Requests missing these headers will be rejected by the server

Required API Headers#

Authorization – Bearer Token#

How it works#

Important Security Notice#

X-Partner-ID – Partner Identification#

Final Checklist#

Required API Headers

Authorization – Bearer Token

How it works

Important Security Notice

X-Partner-ID – Partner Identification

Final Checklist