Developer Documentation
Integrate JoltSMS into your applications and AI agent workflows. Authenticate with API keys, manage numbers and messages via REST, or use the MCP server for automated OTP verification.
curl -H "Authorization: Bearer jolt_sk_your_key_here" \
https://api.joltsms.com/v1/numbersAuthentication
Create API keys, authenticate requests with Bearer tokens, and understand rate limits and error responses.
- API key creation and format
- Bearer token authentication
- Rate limits and pagination caps
- Error responses (401, 403)
- Session-only endpoints
- View full guide
API Reference
Full endpoint reference for numbers, messages, billing, notifications, and team management. Includes request/response examples.
- Numbers — list, provision, update
- Messages — list, search, mark read
- Billing — subscriptions, invoices
- Notifications — endpoints, rules, logs
- Team — invitations, members, roles
- View full guide
MCP Server
Set up the JoltSMS MCP server for AI agent workflows. Provision numbers, poll for SMS, and extract OTP codes programmatically.
- Installation and configuration
- Claude Code and Claude Desktop setup
- Tool reference (7 tools)
- OTP verification workflow
- Troubleshooting
- View full guide
Webhooks
Receive real-time events when SMS arrives, numbers expire, or billing issues occur. HMAC-SHA256 signed for security.
- Jolt Events v1 format
- Event types (SMS, billing, numbers)
- HMAC-SHA256 verification
- Retry policy and DLQ
- Endpoint setup in dashboard
- View full guide
First number? Order through the dashboard
Your first number must be ordered through the Dashboard to set up your payment method. We require 3D Secure authentication when saving your card, which needs you to be present in the browser. After that, you can provision additional numbers via the API or MCP server and they'll use your saved payment method automatically.
Base URL
All API requests use the following base URL:
https://api.joltsms.com/v1