> ## Documentation Index
> Fetch the complete documentation index at: https://www.bloxs.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Test if your Authorization Key works
## OpenAPI
````json GET /Test
{
"openapi": "3.0.4",
"info": {
"title": "Authorization",
"description": "This is an endpoint to request your JWT token and verify the connection and authorization is working correctly.\n\nThe authorization token consists of 2 things: an API key, API Secret\n##### API Key\nThe API Key belongs to an user within the client application where the connection is made to.\nThis key is used to identify the user and is part of the generated token.\n##### API Secret\nThe API Secret belongs to the client application where the connection is made to.\nThis secret is used to hash the token parts into the authorization token.\n",
"version": "v1"
},
"security": [
{}
],
"tags": [
{
"name": "Authorization"
},
{
"name": "Metadata"
},
{
"name": "Test"
}
],
"paths": {
"/Test": {
"get": {
"tags": [
"Test"
],
"summary": "Test if your Authorization Key works",
"responses": {
"200": {
"description": "OK"
}
},
"x-d360-narrative-url": "Test
The Test endpoint lets a developer verify that a previously issued authorization token is valid and accepted by the API, without performing any business operation. It is typically called right after authentication, or when troubleshooting integration issues, to confirm the Bearer token is being sent correctly and is still active. A valid token returns 200 OK, while a missing, invalid, or expired token returns 401 Unauthorized.
Request Fields
Field | Type | Required | Description |
|---|
Authorization (header) | string | Yes | Bearer token obtained from the Authorization endpoint, sent as Bearer {token}. A missing, invalid, or expired token results in a 401 Unauthorized response. A valid, non-expired token returns a 200 OK response. |
Response Fields
No response fields. A 200 status code confirms the token is valid; no response body is returned.
"
}
}
}
}
````