Authorization HTTP header is required.
Basic Authentication
To consume an endpoint using Basic Authentication, theAuthorization HTTP header should be filled with prefixed with the following string: Basic and the available credentials encoded in Base64 format.
Authorization: Basic BASE64_ENCODED_CREDENTIALS
JWT Authentication
Before consuming any endpoint, each client needs to be authenticated with the API providing the authentication credentials. If the authentication is successful, a JWTaccess token is provided. This token can, then, be used in each subsequent API request so for the client to be authorised to access each the resource.
GET JWT ACCESS TOKEN
See below the details of the authentication request to acquire the JWT access token.Resource [POST]
[/auth/jwt/token/]
Request
Response
Example cURL
ACCESSING API RESOURCES
If the client is authenticated successfully, a JWT access token and a refresh token are returned. To consume an endpoint using JWT Authentication, theAuthorization HTTP header should be filled with the acquired JWT access token prefixed with the following string: Bearer .
Authorization: Bearer JWT_ACCESS_TOKEN
REFRESH JWT ACCESS TOKEN
JWT access tokens are expiring for security purposes. In such case, the JWT access token gets invalided and a new one should be acquired. To get a new JWT access token, client can use the provided refresh token from the/auth/jwt/token/ response. See below the details of the authentication request.
Resource [POST]
[/auth/jwt/token/refresh/]