Signup security
Create account
Sign up with email or Google. Use a unique password that has not been leaked in a data breach.
Add sender identity
Request a toll-free number, verify a personal number by OTP, or submit a sender ID for admin approval.
Import contacts
Create groups, upload contacts, and keep consent records current before messaging.
Send and measure
Draft a single SMS or campaign, choose a verified sender, then monitor message delivery.
Guides
Operational rules
These are the backend-backed rules the product enforces before allowing sends or account changes.
Numbers and sender IDs
Toll-free numbers are provisioned from inventory. Personal numbers are caller ID only after OTP verification. Sender IDs require admin review.
Sending rules
SMS sends are blocked unless the selected sender identity is verified or approved. Messages are stored with status for tracking.
Billing and wallet
Wallet credits are stored per account in USD. Each successful send writes a transaction and updates the wallet balance.
API access
API keys belong to the signed-in user and should only be used from trusted systems. Rotate keys when access changes.
API sending checklist
- Use an active API key
- Send from a verified number or approved sender ID
- Store contacts with consent
- Check wallet balance before high-volume sends
- Read message status after send
Example request
POST /api/messages
Authorization: Bearer YOUR_API_KEY
{
"from": "XELLIO",
"to": "+14155550123",
"body": "Your order is ready for pickup."
}