Table of Contents
- • Why VerifyPulse API
- • Quick Start (cURL & JS)
- • Core Endpoints
- • Webhooks & Polling
- • Security & Rate Limits
- • Error Handling
Why VerifyPulse API
Multi-Provider Uptime
Aggregate availability across three providers for best-in-class delivery rates, globally.
Simple, Predictable Pricing
Pay-as-you-go for one-time codes or long-term numbers—no surprise fees.
Fast Onboarding
Start verifying in minutes with clear docs, SDK-friendly responses, and examples.
Global Coverage
Numbers across regions to match your compliance and deliverability needs.
Quick Start
Authenticate
curl -X POST "https://api.verifypulse.com/v1/auth/login" -H "Content-Type: application/json" -d '{"email":"[email protected]","password":"your-password"}'Request a Number
curl -X POST "https://api.verifypulse.com/v1/numbers/request" -H "Authorization: Bearer YOUR_API_KEY" -H "Content-Type: application/json" -d '{"service":"generic","country":"US"}'Check Messages
curl -X GET "https://api.verifypulse.com/v1/sms/receive?numberId=NUMBER_ID" -H "Authorization: Bearer YOUR_API_KEY"Core Endpoints
- POST /auth/login — Authenticate and get a token
- POST /numbers/request — Provision a number for a service and country
- GET /sms/receive — Poll for incoming messages
- POST /webhooks — Configure webhooks to receive SMS in real time
- DELETE /numbers/{id} — Release a number when done
Security & Rate Limits
- Rotate API keys regularly and never embed them in client apps
- Use webhooks over polling for scale; implement exponential backoff
- Validate payload signatures on webhook deliveries
- Leverage IP allowlisting for backend integrations