Authorization
The Authorization endpoint issues a JWT access token used to authenticate all subsequent requests to the Bloxs API. A developer calls this endpoint once at the start of an integration session, or whenever the current token has expired, to exchange an API Key and API Secret for a bearer token. The API Key identifies the specific user within the client application, while the API Secret belongs to the client application itself and is used to sign the token; both are required to generate a valid token.
Request Fields
Field | Type | Required | Description |
|---|---|---|---|
apiKey | string | Yes | Identifies the user within the client application making the request. Minimum length of 1 character. |
apiSecret | string | Yes | Secret belonging to the client application, used to sign the generated token. Minimum length of 1 character. |
Response Fields
Field | Type | Required | Description |
|---|---|---|---|
token | string | No | The generated JWT bearer token. Include this in the |
expiration | string (date-time) | Yes | Expiration timestamp of the token, in GMT, valid for 24 hours from issuance. Format is ISO 8601 date-time, e.g. |
The authorization token created
The authorization token can't be created