Base URL
All API requests should be made to:API Versions
| Version | Status | Notes |
|---|---|---|
| v1 | Deprecated | Legacy API, includes deprecation headers |
| v2 | Current | Production API with enhanced endpoints and features |
Authentication
All API requests require authentication using an API key passed in theX-Api-Key header.
The v2 API uses
to for the recipient phone number and list_number for the sending phone number (E.164 format).V2 API (Current)
V2 API Overview
Full v2 API reference with all endpoints
Send Messages
Send single and bulk SMS messages
Contacts
Create, list, and manage contacts
Audiences
Build dynamic audience segments
Schedules
Schedule and automate campaigns
Migration Guide
Upgrade from v1 to v2
V1 API (Deprecated)
Messages (v1)
Send messages (deprecated)
Contacts (v1)
Contact stubs (no-op)
Webhooks
Delivery status webhooks
Error Codes
V1 error reference
Request Format
- All requests must include
Content-Type: application/json - Phone numbers should be in E.164 format (e.g.,
+14155551234) - Request bodies must be valid JSON
Response Format
All responses are JSON with a consistent structure:- Success — V2 (2xx)
- Success — V1 (2xx)
- Error (4xx/5xx)
Deprecation Headers
All v1 API responses include these headers:| Header | Value |
|---|---|
X-API-Deprecated | v1 is deprecated |
Deprecation | true |
API Limits
Trackly SMS does not impose API rate limits. The platform supports up to 50 million messages per minute. See API Limits & Best Practices for payload size limits and batch guidance.SDKs & Libraries
Currently, we recommend using standard HTTP libraries in your preferred language:Next Steps
Send First SMS
Get started with a quick tutorial
V2 API Overview
Explore the full v2 API