Hyperion

answerRequest

Testing Env

https://{{host}}:8092

POST

/json-rpc/authorize/token/accept

Websocket

Request Example

Shell

JavaScript

Java

Swift

curl --location -g --request POST 'https://localhost:8092/json-rpc/authorize/token/accept' \
--header 'Content-Type: application/json' \
--data-raw '{
    "command": "authorize",
    "subcommand": "answerRequest",
    "id": "7H-yJ",
    "accept": true,
    "tan": 4711
}'

Response Example

HTTP/S not supported

{
    "command": "authorize-answerRequest",
    "error": "Command not supported via single API calls using HTTP/S",
    "success": false,
    "tan": 4711
}

Request

Body Params application/json

command

enum<string>

required

Main instruction field. For authentication, always set to 'authorize'.

Allowed value:

authorize

subcommand

enum<string>

required

Defines the specific authorization action, such as login, logout, etc.

Allowed value:

answerRequest

string

required

Unique identifier for a token (usually 5 characters).

>= 5 characters<= 5 characters

boolean

required

Boolean to accept or deny a token request.

tan

integer

optional

Transaction number for tracking requests and responses.

>= 0

Example:

4711

Examples

Responses

🟢200Success

application/json

Body

command

string

required

The command executed

subcommand

string

optional

The sub-command executed

success

boolean

required

Result, if the request excuted successfully

info

object

optional

Information requested

Additional properties

integer | number | string | boolean

optional

error

string

optional

Reason why a request did not execute successfully

errorData

array [object {1}]

optional

Detailed error explaination

description

string

optional

tan

integer

required

Request's transaction number

Modified at 2025-05-18 08:35:46

newPassword

getPendingTokenRequests