Login users using one-time login methods like magic links or OTPs. This implements a backend-to-backend integration for authentication.
One-Time Login
URI that receives a code when the user clicks the email link. This is your server GET endpoint used to complete the authentication, and should accept 'code' as a query parameter. This URI must be configured as an allowed redirect URI for your Transmit client.
An opaque string that is used to maintain state between the request and the callback. It will be added to the redirect URI as a query parameter, which should be validated by your server to protect against cross-site request forgery (CSRF) attacks
The request ID can serve as an additional security identifier for authentication requests. When set to 'false' (by default), the request ID isn't returned. When set to 'true', Mosaic generates a unique request ID that must be included in the subsequent Authenticate OTP request along with other required parameters.
- Sandbox environmenthttps://api.sbx.transmitsecurity.io/cis/v1/auth/link/email/send
- Production environment (US)https://api.transmitsecurity.io/cis/v1/auth/link/email/send
- Production environment (EU)https://api.eu.transmitsecurity.io/cis/v1/auth/link/email/send
- Production environment (CA)https://api.ca.transmitsecurity.io/cis/v1/auth/link/email/send
- Production environment (AU)https://api.au.transmitsecurity.io/cis/v1/auth/link/email/send
- cURL
- Node.js
- Go
- JavaScript
- Java
- Python
curl -i -X POST \
https://api.sbx.transmitsecurity.io/cis/v1/auth/link/email/send \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"email": "name@example.com",
"redirect_uri": "https://www.example.com/verify",
"email_content": {
"subject": "string",
"primaryColor": "#6981FF",
"base64logo": "string",
"headerText": "string",
"bodyText": "string",
"linkText": "string",
"infoText": "string",
"footerText": "If you didn'\''t request this email, you can safely ignore it.",
"senderName": "string"
},
"state": "string",
"email_expiration": 0,
"channel": "email",
"client_attributes": {
"user_agent": "string",
"ip_address": "string"
},
"generate_request_id": false
}'{ "message": "Email sent successfully" }
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.
- Sandbox environmenthttps://api.sbx.transmitsecurity.io/cis/v1/auth/link/email/authenticate
- Production environment (US)https://api.transmitsecurity.io/cis/v1/auth/link/email/authenticate
- Production environment (EU)https://api.eu.transmitsecurity.io/cis/v1/auth/link/email/authenticate
- Production environment (CA)https://api.ca.transmitsecurity.io/cis/v1/auth/link/email/authenticate
- Production environment (AU)https://api.au.transmitsecurity.io/cis/v1/auth/link/email/authenticate
- cURL
- Node.js
- Go
- JavaScript
- Java
- Python
curl -i -X POST \
https://api.sbx.transmitsecurity.io/cis/v1/auth/link/email/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",
"code": "string",
"request_id": "string"
}'{ "access_token": "string", "id_token": "string", "refresh_token": "string", "token_type": "string", "expires_in": 3600, "session_id": "string" }
Type of user identifier used for login
User identifier, which may correspond to the user's email, phone number, username, or user ID. The type of identifier should be specified as the identifier_type.
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.
Custom email to send the OTP to, can be different than the user's email (if the channel is email)
Custom phone number to send the OTP to, can be different than the user's phone number (if the channel is sms)
The request ID can serve as an additional security identifier for authentication requests. When set to 'false' (by default), the request ID isn't returned. When set to 'true', Mosaic generates a unique request ID that must be included in the subsequent Authenticate OTP request along with other required parameters.
- Sandbox environmenthttps://api.sbx.transmitsecurity.io/cis/v1/auth/otp/send
- Production environment (US)https://api.transmitsecurity.io/cis/v1/auth/otp/send
- Production environment (EU)https://api.eu.transmitsecurity.io/cis/v1/auth/otp/send
- Production environment (CA)https://api.ca.transmitsecurity.io/cis/v1/auth/otp/send
- Production environment (AU)https://api.au.transmitsecurity.io/cis/v1/auth/otp/send
- cURL
- Node.js
- Go
- JavaScript
- Java
- Python
curl -i -X POST \
https://api.sbx.transmitsecurity.io/cis/v1/auth/otp/send \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"channel": "sms",
"identifier_type": "email",
"identifier": "string",
"email_content": {
"subject": "string",
"primaryColor": "#6981FF",
"base64logo": "string",
"headerText": "string",
"bodyText": "string",
"linkText": "string",
"infoText": "string",
"footerText": "If you didn'\''t request this email, you can safely ignore it.",
"senderName": "string"
},
"custom_sms_input": {
"custom_message": "string",
"sender_id": "string"
},
"approval_data": {
"transaction_id": "eFII2y40uB9hQ98nXt3tc1IHkRt8GrRZiqZuRn_59wT",
"sum": "200"
},
"custom_email": "string",
"custom_phone_number": "string",
"client_attributes": {
"user_agent": "string",
"ip_address": "string"
},
"expires_in": 0,
"generate_request_id": false
}'{ "message": "OTP sent", "approval_data": { "transaction_id": "eFII2y40uB9hQ98nXt3tc1IHkRt8GrRZiqZuRn_59wT", "sum": "200" }, "code": "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 request additional claims in the ID token, such as roles, permissions, and other user profile data. The structure is per the OIDC Standard. For supported claims and how to request custom claims, see the ID Token Reference.
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 sending the OTP
- Sandbox environmenthttps://api.sbx.transmitsecurity.io/cis/v1/auth/otp/authenticate
- Production environment (US)https://api.transmitsecurity.io/cis/v1/auth/otp/authenticate
- Production environment (EU)https://api.eu.transmitsecurity.io/cis/v1/auth/otp/authenticate
- Production environment (CA)https://api.ca.transmitsecurity.io/cis/v1/auth/otp/authenticate
- Production environment (AU)https://api.au.transmitsecurity.io/cis/v1/auth/otp/authenticate
- cURL
- Node.js
- Go
- JavaScript
- Java
- Python
curl -i -X POST \
https://api.sbx.transmitsecurity.io/cis/v1/auth/otp/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",
"passcode": "string",
"identifier_type": "email",
"identifier": "string",
"request_id": "string"
}'{ "access_token": "string", "id_token": "string", "refresh_token": "string", "token_type": "string", "expires_in": 3600, "session_id": "string" }