Authentication
Last updated
Last updated
The OffBlocks API utilises the Bearer authentication mechanism. Before accessing any of the authenticated endpoints, you must obtain an authentication token by providing your client credentials: apiKey
and apiSecret
. This process is automatically handled for all requests in our Postman collection.
The endpoint mentioned above returns a JSON Web Token (JWT) token. You must include this token as a Bearer token in the header of all requests that require authentication. Additionally, the response includes an expiration timestamp for the token, measured in seconds.
Should you suspect that your credentials have been compromised, you can update them using the following endpoint:
This endpoint allows you to replace your current apiKey
and apiSecret
with new, more secure credentials.
If necessary, you can completely remove your API credentials by using the following endpoint:
Please exercise caution when using this endpoint, as it will permanently revoke your access to the OffBlocks API.
Retrieve authentication token using API credentials
/auth/token
Unique API key used to identify your API integration. Note this can be different for live and sandbox environments
API secret
Add or update API credentials. If credentials are updated this action invalidates all issued tokens and active sessions
/auth/credentials
Unique API key used to identify your API integration. Note this can be different for live and sandbox environments
API secret
No body
Delete existing API credentials. This invalidates all issued tokens and active sessions
/auth/credentials
Unique API key used to identify your API integration. Note this can be different for live and sandbox environments
No body