Start token activation
POST/api/web/v1/tokens/:tokenid/activation
Start activation of the given token. Caller requires the TOKENS:ADD permission.
Request
Path Parameters
The UUID of the token to be activated.
- application/json
Body
A flag indicating if Identity as a Service should send an activation email including the activation information to the end user. If not specified, this attribute defaults to false.
A flag indicating if the QR code for offline activation is returned. The link encoded in the QR code is always returned for clients that want to encode their own QR code. If not specified, this attribute defaults to false.
Possible values: [CLASSIC
, ONLINE
, OFFLINE
]
The list of activation types that will be performed. Allowed values are: CLASSIC (return activation values that must be manually entered into the mobile application), ONLINE (return a link that when clicked will launch the mobile application) and OFFLINE (return a QR code that can be scanned by the mobile application). If no values are specified in the list, then all activation types are performed.
Responses
- 200
- 400
- 401
- 403
- 404
- 409
Successful
- application/json
- Schema
- Example (from schema)
Schema
The activation address for the token. This value should be entered into the Mobile ST application if you want to perform manual activaiton.
The activation code for the token. This value should be entered into the Mobile ST application if you want to perform manual activation
The HTTP activation URL. Clicking on this URL on your mobile device will redirect you to the Mobile ST application to perform activation.
The application specific activation URL. Clicking on this URL on your mobile device will launch the Mobile ST application to perform activation.
If the Mobile ST prompts you to enter an activation password during activation, this attribute is the password you must enter.
The base-64 encoded activation QR code. This QR code can be scanned by the Mobile ST application to perform activation.
The URL encoded in the activation QR code.
The serial number of the token.
{
"activationAddress": "string",
"activationCode": "string",
"activationOnlineHttpURL": "string",
"activationOnlineURL": "string",
"activationPassword": "string",
"activationQRCode": "string",
"activationURL": "string",
"serialNumber": "string"
}
Bad Request
- application/json
- Schema
- Example (from schema)
Schema
Error Codes specific to cause of failure.
Additional Error Message describing the error.
Optional additional error information.
{
"errorCode": "invalid_user_response",
"errorMessage": "Application id cannot be null",
"parameters": [
{}
]
}
Access denied
- application/json
- Schema
- Example (from schema)
Schema
Error Codes specific to cause of failure.
Additional Error Message describing the error.
Optional additional error information.
{
"errorCode": "invalid_user_response",
"errorMessage": "Application id cannot be null",
"parameters": [
{}
]
}
Forbidden
- application/json
- Schema
- Example (from schema)
Schema
Error Codes specific to cause of failure.
Additional Error Message describing the error.
Optional additional error information.
{
"errorCode": "invalid_user_response",
"errorMessage": "Application id cannot be null",
"parameters": [
{}
]
}
Not Found
- application/json
- Schema
- Example (from schema)
Schema
Error Codes specific to cause of failure.
Additional Error Message describing the error.
Optional additional error information.
{
"errorCode": "invalid_user_response",
"errorMessage": "Application id cannot be null",
"parameters": [
{}
]
}
Conflict
- application/json
- Schema
- Example (from schema)
Schema
Error Codes specific to cause of failure.
Additional Error Message describing the error.
Optional additional error information.
{
"errorCode": "invalid_user_response",
"errorMessage": "Application id cannot be null",
"parameters": [
{}
]
}