API-first experience

Developers

Build transactional SMS, bulk campaign, WhatsApp, and automation workflows from one API surface.

Use WhySMS for SMS OTP, verification workflows, authentication messaging, delivery reports, sender IDs, and event-based messaging without splitting tools by team.

Open API Docs Start Free Trial Talk to Sales Engineering

PHP Node.js Python Java cURL HTTP

Get started fast

Move from evaluation to first OTP or transactional API call with a lightweight onboarding path and clear technical CTAs.

Build by workflow

Cover verification codes, authentication messaging, campaign requests, WhatsApp templates, and event-triggered updates from one place.

Ship operationally

Give engineering, growth, and support teams one messaging workflow with shared status visibility.

Code examples

Give technical visitors an immediate sense of how the platform will fit into their stack.

Send OTP code cURL

curl --request POST 'https://staging.whysms.com/api/v1/status' \
  --header 'Accept: application/json' \
  --data 'channel=sms&type=otp&flow=login_verification'

Verification workflow JSON

{
  "channel": "sms",
  "use_case": "password_reset",
  "code_length": 6,
  "delivery_report": true
}

Authentication messaging JavaScript

const authMessage = {
  channel: 'sms',
  use_case: '2fa',
  flow: 'account_security',
  delivery_report: true
};

Developer paths

Move from documentation to implementation without friction.

The public docs entry should support product evaluation, first API discovery, and later handoff into deeper technical material or solution discussions.

Documentation Public API Index Request implementation support