Verify Push API
Verify Push endpoints exposed by the Devotel CPaaS API Base path:/api/v1/verify/push
Endpoint count: 4
Verify a push challenge signature
POST /api/v1/verify/push/challenges/{challengeId}/verifyapproved, factor flips to verified. On mismatch: attempts increment; auto-denied at maxAttempts.
—
The device’s base64-encoded signature over the challenge signing string factorId.challengeId.nonce (1–4096 characters).
Register a push factor
POST /api/v1/verify/push/factorsStable identifier for the end user this device belongs to — your user id, email, or username (1–255 characters).
Human-readable label for the paired device, shown when the user reviews their registered factors (1–120 characters).
Signature algorithm of the device key pair —
ed25519 or ecdsa-p256.The device’s base64-encoded public key. The matching private key never leaves the device; it signs each challenge (1–4096 characters).
Encoding of
publicKey — raw for a bare key or spki for a SubjectPublicKeyInfo-wrapped key.Optional push-token id (FCM, APNs, or Web Push) the service uses to deliver challenge notifications to this device (1–120 characters).
Optional free-form key/value bag — device model, OS version, attestation chain. The caller defines the contract.
Issue a push challenge
POST /api/v1/verify/push/factors/{factorId}/challenges<factorId>.<challengeId>.<nonce> and submits the signature via /verify/push/challenges/:challengeId/verify.
—
Human-readable prompt shown in the push notification so the user knows what they are approving, e.g. the action or device (1–280 characters).
Lifetime of the issued challenge, in seconds, before it expires. Defaults to 120; range 30–600.
Revoke a push factor
POST /api/v1/verify/push/factors/{factorId}/revoke—