Issue API user pairing token
Issues a device pairing token for the given user and returns the user’s info along with the token.
- The API user must be in PENDING_ACTIVATION status. If the user is already set up (enabled), the request is rejected with a 409 Conflict.
- Please note that this endpoint is available only for API keys with Owner/Admin/Non Signing Admin permissions. Endpoint Permission: Owner, Admin, Non-Signing Admin.
POST
TypeScript
Headers
A unique identifier for the request. If the request is sent multiple times with the same idempotency key, the server will return the same response as the first request. The idempotency key is valid for 24 hours.
Path Parameters
The ID of the api user
Response
Pairing token issued
The unique identifier of the user
The role of the user
Available options:
OWNER, ADMIN, SIGNER, COLLATERALS_SIGNER, EDITOR, APPROVER, VIEWER, NON_SIGNING_ADMIN, AUDITOR, NCW_ADMIN, NCW_SIGNER, SECURITY_ADMIN, SECURITY_AUDITOR Whether the user is enabled
The device pairing token issued for the given user
Example:
"access-token-for-pairing"
The name of the user
Example:
"John Doe"
The type of the user
Available options:
API, CONSOLE The status of the user
Available options:
PENDING_ACTIVATION, PENDING_DEVICE_PAIRING, PENDING_DEVICE_SETUP, READY Previous
Resets deviceResets mobile device for given console user, that user will need to do mobile onboarding again.
- Please note that this endpoint is available only for API keys with Admin/Non Signing Admin permissions.
Endpoint Permission: Admin, Non-Signing Admin.
Next
TypeScript