Who This API is For
This API is designed for organizations that need to send and receive SMS directly from their own systems, rather than through a user interface.
It’s best suited for technical teams or organizations working with developers to integrate SMS into existing systems and workflows.
-
Development teams integrating SMS into applications
-
Organizations with existing systems (CRM, EMR, scheduling, case management)
-
Operations teams automating reminders and notifications
-
Security and IT teams supporting verification (2FA, one time passcodes) and system alerts
Core Capabilities
Supported out of the box:
• Programmatic sending of SMS and MMS
• Two-way messaging via webhooks (inbound replies delivered to your system)
• Delivery status callbacks (sent, delivered, failed, etc.)
• Dedicated, verified toll-free number provisioning
• Email-to-SMS routing (optional)
• Canada and USA messaging
Designed for:
• Transactional and system-generated messages
• Notifications and reminders
• OTP / 2FA and verification workflows
• Operational alerts and status updates
How It Works
- Your system sends a message request to the API.
- Messages are delivered through Canadian/USA carrier networks using a verified toll-free number.
- Delivery status updates are returned to your system via webhook.
- Incoming replies are delivered to your webhook endpoint for processing.
Two-way messaging is fully supported, with all inbound messages handled through webhooks to ensure clean system-to-system integration.
Number Provisioning, Consent & CASL
To protect deliverability and comply with carrier policies:
- Messages are sent from a dedicated, verified toll-free number or short code.
- 10-digit long codes cannot be used for bulk or API-driven messaging in Canada.
- Express consent must be demonstrated as part of the number approval process.
- Stop requests must be respected.
- Use cases are reviewed prior to provisioning to confirm compliance and suitability.
This process ensures alignment with CASL requirements and protects both your organization and message recipients.
Example Use Cases
Notifications & Reminders
Appointment reminders, service updates, schedule changes, and system alerts.
Security & verification
OTP, 2FA, and account verification messages sent programmatically.
Two-way system workflows
Structured SMS interactions where replies are processed by your application.
Getting Started
- Request API documentation
- We review your use case, volume expectations, and consent model
- A dedicated toll-free number is provisioned and verified
- You receive credentials and test access
Most organizations are able to begin testing shortly after approval.
Frequently Asked Questions
Do you support two-way messaging?
Yes. Incoming messages are delivered to your system via webhooks.
Is MMS supported?
Yes. MMS is supported through the API. Standard throughput for MMS is 1 msg/second (vs 3 msg/second for SMS).
Can we use our existing phone number?
No. A dedicated, verified toll-free number is required for bulk or API-driven messaging.
How is consent handled?
Express consent must be demonstrated during number provisioning. Guidance is provided during onboarding.
Do you support email-to-SMS?
Yes. Email-to-SMS is available as part of the API.
Do you support OTP / 2FA use cases?
Yes.
Request API Documentation
Tell us where to send the API documentation. If you have any other questions, send them along.