Login using time-based one-time passcodes (TOTP), which can be generated by authenticator apps like Google Authenticator. This provides passwordless, two-factor authentication using a single login method.
TOTP
Resource URI the authentication request is attempting to access, which is reflected in the audience (aud claim) of the access token. This must be configured as resource for the application.
Used to associate the authentication with an existing session (such as for MFA). If unspecified, a new session is created and the session ID is returned.
Type of user identifier used for validating the TOTP
- Sandbox environmenthttps://api.sbx.transmitsecurity.io/cis/v1/auth/totp/authenticate
- Production environment (US)https://api.transmitsecurity.io/cis/v1/auth/totp/authenticate
- Production environment (EU)https://api.eu.transmitsecurity.io/cis/v1/auth/totp/authenticate
- Production environment (CA)https://api.ca.transmitsecurity.io/cis/v1/auth/totp/authenticate
- Production environment (AU)https://api.au.transmitsecurity.io/cis/v1/auth/totp/authenticate
- cURL
- Node.js
- Go
- JavaScript
- Java
- Python
curl -i -X POST \
https://api.sbx.transmitsecurity.io/cis/v1/auth/totp/authenticate \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"resource": "string",
"claims": {
"id_token": {
"roles": null
}
},
"org_id": "string",
"client_attributes": {
"user_agent": "string",
"ip_address": "string"
},
"session_id": "string",
"token": "string",
"identifier_type": "email",
"identifier": "string"
}'{ "access_token": "string", "id_token": "string", "refresh_token": "string", "token_type": "string", "expires_in": 3600, "session_id": "string" }
Resource URI the authentication request is attempting to access, which is reflected in the audience (aud claim) of the access token. This must be configured as resource for the application.
Used to associate the authentication with an existing session (such as for MFA). If unspecified, a new session is created and the session ID is returned.
Flat object that contains the data that your customer should approve for a transaction signing or custom approval flow. It can contain up to 10 keys, and only alphanumeric characters, underscores, hyphens, and periods. It will be returned as a claim in the ID token upon successful authentication.
Type of user identifier used for login
- Sandbox environmenthttps://api.sbx.transmitsecurity.io/cis/v1/auth/totp/transaction/start
- Production environment (US)https://api.transmitsecurity.io/cis/v1/auth/totp/transaction/start
- Production environment (EU)https://api.eu.transmitsecurity.io/cis/v1/auth/totp/transaction/start
- Production environment (CA)https://api.ca.transmitsecurity.io/cis/v1/auth/totp/transaction/start
- Production environment (AU)https://api.au.transmitsecurity.io/cis/v1/auth/totp/transaction/start
- cURL
- Node.js
- Go
- JavaScript
- Java
- Python
curl -i -X POST \
https://api.sbx.transmitsecurity.io/cis/v1/auth/totp/transaction/start \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"resource": "string",
"claims": {
"id_token": {
"roles": null
}
},
"org_id": "string",
"client_attributes": {
"user_agent": "string",
"ip_address": "string"
},
"session_id": "string",
"approval_data": {
"transaction_id": "eFII2y40uB9hQ98nXt3tc1IHkRt8GrRZiqZuRn_59wT",
"sum": "200"
},
"identifier_type": "email",
"identifier": "string"
}'{ "approval_data": { "transaction_id": "eFII2y40uB9hQ98nXt3tc1IHkRt8GrRZiqZuRn_59wT", "sum": "200" }, "challenge": "123456" }
Resource URI the authentication request is attempting to access, which is reflected in the audience (aud claim) of the access token. This must be configured as resource for the application.
Used to associate the authentication with an existing session (such as for MFA). If unspecified, a new session is created and the session ID is returned.
Type of user identifier used for validating the TOTP
- Sandbox environmenthttps://api.sbx.transmitsecurity.io/cis/v1/auth/totp/transaction/authenticate
- Production environment (US)https://api.transmitsecurity.io/cis/v1/auth/totp/transaction/authenticate
- Production environment (EU)https://api.eu.transmitsecurity.io/cis/v1/auth/totp/transaction/authenticate
- Production environment (CA)https://api.ca.transmitsecurity.io/cis/v1/auth/totp/transaction/authenticate
- Production environment (AU)https://api.au.transmitsecurity.io/cis/v1/auth/totp/transaction/authenticate
- cURL
- Node.js
- Go
- JavaScript
- Java
- Python
curl -i -X POST \
https://api.sbx.transmitsecurity.io/cis/v1/auth/totp/transaction/authenticate \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"resource": "string",
"claims": {
"id_token": {
"roles": null
}
},
"org_id": "string",
"client_attributes": {
"user_agent": "string",
"ip_address": "string"
},
"session_id": "string",
"token": "string",
"identifier_type": "email",
"identifier": "string"
}'{ "access_token": "string", "id_token": "string", "refresh_token": "string", "token_type": "string", "expires_in": 3600, "session_id": "string" }
Request
Registers a TOTP authenticator for the logged-in user. The response contains the secret and other configuration that will be used to generate TOTP codes for authentication. The app must provide it to the user (such as via QR) so the user can complete the process using their authenticator app.
Note:
- A TOTP authenticator is considered registered even if it wasn't added to an authenticator app.
- A user can only have a single TOTP authenticator for a given application. Attempting to register another will fail, unless your request enables override or you first revoke the authenticator that's currently registered.
Account name displayed in the authenticator app. If unspecified, the user's email, username, or phone number will be used (ordered by preference).
- Sandbox environmenthttps://api.sbx.transmitsecurity.io/cis/v1/users/me/totp
- Production environment (US)https://api.transmitsecurity.io/cis/v1/users/me/totp
- Production environment (EU)https://api.eu.transmitsecurity.io/cis/v1/users/me/totp
- Production environment (CA)https://api.ca.transmitsecurity.io/cis/v1/users/me/totp
- Production environment (AU)https://api.au.transmitsecurity.io/cis/v1/users/me/totp
- cURL
- Node.js
- Go
- JavaScript
- Java
- Python
curl -i -X POST \
https://api.sbx.transmitsecurity.io/cis/v1/users/me/totp \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"label": "John Doe",
"allow_override": false
}'{ "secret": "string", "uri": "string" }
- Sandbox environmenthttps://api.sbx.transmitsecurity.io/cis/v1/users/me/totp/revoke
- Production environment (US)https://api.transmitsecurity.io/cis/v1/users/me/totp/revoke
- Production environment (EU)https://api.eu.transmitsecurity.io/cis/v1/users/me/totp/revoke
- Production environment (CA)https://api.ca.transmitsecurity.io/cis/v1/users/me/totp/revoke
- Production environment (AU)https://api.au.transmitsecurity.io/cis/v1/users/me/totp/revoke
- cURL
- Node.js
- Go
- JavaScript
- Java
- Python
curl -i -X POST \
https://api.sbx.transmitsecurity.io/cis/v1/users/me/totp/revoke \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"authenticator_id": "string"
}'- Sandbox environmenthttps://api.sbx.transmitsecurity.io/cis/v1/users/{userId}/totp/revoke
- Production environment (US)https://api.transmitsecurity.io/cis/v1/users/{userId}/totp/revoke
- Production environment (EU)https://api.eu.transmitsecurity.io/cis/v1/users/{userId}/totp/revoke
- Production environment (CA)https://api.ca.transmitsecurity.io/cis/v1/users/{userId}/totp/revoke
- Production environment (AU)https://api.au.transmitsecurity.io/cis/v1/users/{userId}/totp/revoke
- cURL
- Node.js
- Go
- JavaScript
- Java
- Python
curl -i -X POST \
'https://api.sbx.transmitsecurity.io/cis/v1/users/{userId}/totp/revoke' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"authenticator_id": "string"
}'