Indicates that the auth device has engaged in the flow, such as when the user scans a QR encoding the cross-device ticket ID. This updates the flow status to scanned.
- Sandbox environmenthttps://api.sbx.transmitsecurity.io/cis/v1/auth/webauthn/cross-device/attach-device
- US production environmenthttps://api.transmitsecurity.io/cis/v1/auth/webauthn/cross-device/attach-device
- EU production environmenthttps://api.eu.transmitsecurity.io/cis/v1/auth/webauthn/cross-device/attach-device
- CA production environmenthttps://api.ca.transmitsecurity.io/cis/v1/auth/webauthn/cross-device/attach-device
- AU production environmenthttps://api.au.transmitsecurity.io/cis/v1/auth/webauthn/cross-device/attach-device
- JP production environmenthttps://api.gasne1-ts01.transmitsecurity.io/cis/v1/auth/webauthn/cross-device/attach-device
curl -i -X POST \
https://api.sbx.transmitsecurity.io/cis/v1/auth/webauthn/cross-device/attach-device \
-H 'Content-Type: application/json' \
-d '{
"cross_device_ticket_id": "string"
}'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.
Example:
{ "transaction_id": "eFII2y40uB9hQ98nXt3tc1IHkRt8GrRZiqZuRn_59wT", "sum": "200" }
Response
{ "status": "pending", "started_at": "string", "approval_data": { "transaction_id": "eFII2y40uB9hQ98nXt3tc1IHkRt8GrRZiqZuRn_59wT", "sum": "200" } }