This page is for Taurus PROTECT, version v3.56.
For other versions, use one of these documentation indexes:
- v3.58 (default): https://taurushq.ferndocs.com/protect-capital/v3.58/llms.txt
- v3.56: https://taurushq.ferndocs.com/protect-capital/v3.56/llms.txt
- v3.54: https://taurushq.ferndocs.com/protect-capital/v3.54/llms.txt
- v3.52: https://taurushq.ferndocs.com/protect-capital/v3.52/llms.txt
- v3.50: https://taurushq.ferndocs.com/protect-capital/v3.50/llms.txt
- v3.48: https://taurushq.ferndocs.com/protect-capital/v3.48/llms.txt
- v3.46: https://taurushq.ferndocs.com/protect-capital/v3.46/llms.txt
- v3.44: https://taurushq.ferndocs.com/protect-capital/v3.44/llms.txt
- v3.42: https://taurushq.ferndocs.com/protect-capital/v3.42/llms.txt
- v3.40: https://taurushq.ferndocs.com/protect-capital/v3.40/llms.txt
- v3.38: https://taurushq.ferndocs.com/protect-capital/v3.38/llms.txt
Starts a user’s device pairing request (Step 2)
POST https://your-protect-instance.example.com / api / rest / v1 / user-device / pairing / :pairingID / start
It starts a specific pairing process. The nonce and user's device encryption key will be used to validate futures requests.
Request This endpoint expects an object.
nonce string Required
A 6 digits number
publicKey string Required
ECDSA publickey encoded in base64 format
Response A successful response.
Errors 503 Service Unavailable Error
