Back to Support
SMS API Overview
THEITBULLS SMS API enables you to send and receive text messages at scale with high reliability and global reach. Our API supports bulk SMS, personalized messaging, two-way communication, and real-time delivery tracking.
Key Features
- Bulk SMS: Send thousands of messages with a single API call
- Two-Way Communication: Enable SMS replies and conversations
- Personalization: Dynamically customize each message with variables
- Delivery Tracking: Real-time status updates and delivery reports
- Global Coverage: Reach users in 180+ countries with local sender IDs
- Opt-Out Management: Automatic handling of STOP and unsubscribe requests
Getting Started
To start using the SMS API, you need to generate your API keys from the dashboard and make your first API call. Here's a simple example:
curl -X POST https://api.theitbulls.com/v1/sms/send \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"to": "911234567890",
"from": "THEITBULLS",
"text": "Hello from THEITBULLS SMS API!"
}'
💡 Tip: Always test in sandbox mode first before sending real messages. Use test credentials to verify your integration.
Bulk SMS Campaigns
Our SMS API supports bulk messaging for campaigns, alerts, and notifications. You can send to multiple recipients with personalized content using template variables.
curl -X POST https://api.theitbulls.com/v1/sms/bulk \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"messages": [
{"to": "911234567890", "text": "Hello John!"},
{"to": "911234567891", "text": "Hello Sarah!"}
]
}'
Two-Way SMS
Enable two-way communication with your customers. Our SMS API supports inbound message handling via webhooks, allowing you to receive and respond to SMS replies in real-time.
- Set up webhook URLs to receive incoming messages
- Respond automatically with customizable replies
- Track conversation history and customer engagement
Best Practices
- Use sandbox: Always test in sandbox environment before production
- Handle delivery reports: Monitor status_callback for delivery updates
- Manage opt-outs: Respect STOP requests immediately
- Rate limiting: Respect API rate limits to avoid throttling
- Message templates: Use pre-approved templates for compliance
Error Codes
- 400: Bad Request — Invalid parameters or missing fields
- 401: Unauthorized — Invalid or missing API key
- 403: Forbidden — Insufficient permissions
- 429: Rate Limit Exceeded — Too many requests
- 500: Internal Server Error — Please retry after some time