API Documentation
SMSBAT provides three powerful APIs for different messaging and communication needs:
SMSBAT API
The core messaging API for sending various types of messages including SMS, Viber, RCS, and Flash Call with fallback strategies.
Key Features:
- Multiple message types (SMS, Viber, RCS, Flash Call)
- Fallback messaging when primary delivery fails
- Rich media support (images, videos, PDFs)
- Message status tracking
- OTP notifications
ChatHub API
REST API for managing Viber business chats, client conversations, and customer support automation.
Key Features:
- Company and operator token management
- Organization management
- Operator synchronization
- Widget integration for web applications
- Real-time chat support
Cascade API
Multi-channel messaging API that automatically routes messages across Telegram Bot, Viber Bot, Viber Business Messages, RCS, and SMS with a single request.
Key Features:
- One API request for multi-channel delivery
- Automatic platform routing
- Variable substitution for dynamic content
- Message scheduling
- Time-to-live (TTL) support
Getting Started
- Choose Your API - Select the API that best fits your use case
- Get Credentials - Contact your SMSBAT manager to obtain API credentials
- Review Authentication - Each API uses different authentication methods
- Test Endpoints - Use the provided examples to test integration
- Go Live - Deploy your integration to production
Authentication
Each API uses different authentication methods:
- SMSBAT API: HTTP Basic Auth, API Key Header, or API Key as Password
- ChatHub API: Bearer token (JWT) or
X-Authorization-Keyheader - Cascade API:
X-Authorization-Key,X-Viber-Auth-Token, orX-Tg-Bot-Keyheaders
Support
Need help? Contact our support team:
- Email: [email protected]
- Documentation: developers.smsbat.com
Rate Limits
To ensure system stability, all APIs are subject to rate limiting. By default, messaging endpoints allow up to 100 requests per second.
Error Codes
The SMSBAT APIs use standard HTTP response codes to indicate the success or failure of an API request, along with specific internal business logic codes for detailed troubleshooting.