Alerts and Reminders
Customer Service Ops
Operations
Marketing
Security & ID
Business Continuity Planning
Logistics
Retail
Customer Service
Insurance
Public Sector
Finance
Education
Healthcare
Utility
AWS
Wholesale
Integrations
White-labelled Platform
Code Samples
Glossary
APIs
Product Updates
About 
Contact us 
Modica Careers 
Privacy .svg){kind=small}
Trust Centre .svg){kind=small}
Vulnerability Disclosure Program 
Blog
FAQsIntelligent Messaging API
One integration. A smarter way to deliver.
Connect WhatsApp and SMS through one API. Use intelligent routing and automatic fallback to help important messages reach your customers when the preferred channel fails.
More control over how your messages get there
A failed message can interrupt a customer journey. Give your applications a configurable way to choose a delivery route and switch channels when needed.
Improve resilience
Reduce reliance on a single channel with fallback when the preferred route fails or times out.
Manage delivery costs
Configure routing around viable channels and costs in the markets you serve.
Adapt by market
Choose a messaging strategy that reflects channel availability and customer adoption by destination.
Simplify integration
Connect your systems once and manage configured channels within the same messaging framework.
Send once. Let your delivery rules take it from there.
-
Connect your application
Send your message through one API integration from your application, CRM or business system.
-
Choose your route
Configure the primary channel for your customer journey or market, with a fallback strategy to match.
-
Fall back automatically
If the preferred channel fails or times out, the API uses the next configured channel.
A customer’s WhatsApp notification fails to deliver. Your configured strategy sends the service update by SMS, so the journey can continue.
Illustrative example. Delivery remains subject to channel and network availability.
The right route for your customer journey
Use WhatsApp and SMS together, with routing and fallback configured around your requirements. Your primary channel can vary by journey or destination.
WhatsApp journeys require an active WhatsApp API connection and a dedicated WhatsApp number or source. Applicable message templates and channel requirements also apply.
Support authentication, transactional and marketing journeys through WhatsApp where supported, with SMS as a configured fallback.
SMS
Use SMS as your primary channel or as a fallback when a WhatsApp message fails or times out.
Email fallback
Coming soonEmail fallback is in development. Talk to our team about availability for your use case.
Keep your customer journeys moving
Build routing and fallback into the messages that support account access, everyday updates and customer engagement.
One-time passwords
Help customers complete authentication and account actions with WhatsApp delivery where supported and SMS fallback if delivery fails or times out.
- Registration
- Password resets
- Payment approvals
- Account changes
Example code only. Never share your verification code.
Transactional updates
Keep important notifications moving when the preferred channel is unavailable or unsuccessful.
- Order confirmations
- Delivery updates
- Appointment reminders
- Payment notifications
- Service updates
Illustrative customer notification.
Marketing messages
Extend campaign reach with configured channel fallback, while keeping messaging connected to your existing customer journey.
- Promotions and offers
- Product launches
- Loyalty rewards
- Event invitations
Reply STOP to opt out.
Connect with support from messaging experts
Our team can help you plan your integration, set up messaging sources and define the routing strategy for your use case.
Already using a Modica API? Talk to us about migration from these existing interfaces.
- REST API v1
- REST API v2
- HTTP/S
- SOAP
- RestEmail
-
Set up your messaging sources
Establish the sources and numbers required for the channels you will use.
-
Provision your API connection
Set up the Intelligent Messaging API gateway as the integration point for your application.
-
Configure channels and fallback
Define the primary channel and fallback rules, then test your messaging journey before launch.
Intelligent Messaging API FAQs
Can I use the API for standard SMS messaging?
Yes. You can use the API for standard SMS workflows and add intelligent routing and fallback capabilities to suit your requirements.
What triggers a fallback message?
Fallback follows your configured delivery strategy. If delivery through the primary channel fails or times out, the next configured channel is used. Our team can help you define the routing rules for your setup.
Do I need a WhatsApp account and number?
WhatsApp journeys require an active WhatsApp API connection and a dedicated WhatsApp number or source. Our team can help you understand onboarding and template requirements.
Is email fallback available?
Email fallback is in development. Contact our team to discuss availability and the channels currently supported for your use case.
Can I migrate from an existing Modica API?
Migration paths include REST API v1, REST API v2, HTTP/S, SOAP and RestEmail. Talk to our team about your existing integration and the features you need before planning your transition.
How is the service priced?
Pricing depends on your setup, usage and configured channels. API and channel charges apply, including applicable Meta charges for WhatsApp. Contact our team for a quote based on your requirements.