Send a one-time code by verified business SMS.
Use the SMS send endpoint to queue a code message to a recipient. Your application generates the code, limits attempts, stores it securely, expires it and verifies the response. Skyroute does not provide those application-side OTP controls.
Prepare the recipient, sender and route.
Use an approved sender ID and a scoped API key with sms:send. Supply an E.164 recipient, destination and operator. The route may be selected automatically when eligible. Account, plan, wallet, sender and route checks run when you submit; an API response that queues a message is not a delivery receipt.
Collect the recipient’s permission for the authentication message and follow destination-specific sender and template requirements. Avoid putting passwords or sensitive account details in the SMS body. Do not rely on SMS alone for high-risk account recovery.
Queue the message; verify the code in your app.
The values below illustrate the request shape. Replace the sender, number, destination and operator with approved values for your account. Carrier delivery requires a connected route.
POST /api/v1/sms/send
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
Idempotency-Key: 11111111-1111-4111-8111-111111111111
{"to":["+12025550147"],"message":"Your sign-in code is 448120. It expires in 5 minutes.","sender_id":"YOURID","route":"auto","destination":"United States","operator":"all"}What to measure after submission.
Keep the application request ID beside your own OTP attempt record, then inspect SMS logs or delivery events when configured. Handle a failed or delayed message without revealing whether an account exists. Apply your own resend limit and code expiration; these are not implied by the SMS queue state.
Explore related workflows