API-first experience

Developers

Build with messaging APIs that help product and engineering teams move from pilot to production faster.

Use WhySMS as the entry point for SMS, WhatsApp, OTP, and voice communication workflows. The developer experience should feel lightweight at first contact and reliable at scale.

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 API call with a lightweight onboarding path and clear technical CTAs.

Build by channel

Explore SMS, WhatsApp, OTP, and voice workflows based on your product requirements.

Ship operationally

Align engineering, growth, and support teams around one communications platform.

Code examples

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

Authentication request cURL

curl --request GET 'https://staging.whysms.com/api/v1' \
  --header 'Accept: application/json'

Service discovery JSON

{
  "services_endpoint": "https://staging.whysms.com/api/v1/services",
  "packages_endpoint": "https://staging.whysms.com/api/v1/packages",
  "contact_endpoint": "https://staging.whysms.com/api/v1/contact"
}

Message workflow sketch JavaScript

const communicationFlow = {
  channel: 'sms',
  use_case: 'otp',
  failover: ['voice'],
  audience: 'global_users'
};

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