The short version.You can build on DUMO with our APIs and Developer Cloud. Keep your keys secret, stay within rate limits, and follow the rules for sending messages. Usage is paid in credits. We’ll give notice before breaking changes.
These terms add to the Terms of Service when you use DUMO Developer Cloud, the DUMO APIs, SDKs, webhooks, the Messaging API, the CMS, DEB or Functions (together, the Developer Services).
1. Access and keys
1.1 You get API keys per project, with separate Test and Live keys. Test is free and isolated from Live. A Live key is shown once; store it securely.
1.2 Keep keys secret. Don’t put Live keys in client-side code or public repositories. You’re responsible for all use of your keys. If a key is exposed, rotate it immediately in the console and tell [email protected].
1.3 Going live may require a checklist (for example a verified sending domain or a registered SMS sender ID) and, for some services, our review.
2. Plans and billing
2.1 Developer Cloud is billed as a yearly access fee. Each new Developer workspace receives a one-time allowance of starter credits. Usage of the Developer Services is paid in credits from your wallet at the rates on the pricing page. DEB is free.
2.2 If you send through your own connected provider, that sending is billed by your provider, not in credits.
2.3 If your wallet runs out, Live requests that use credits will be refused until you add credits. You can turn on auto top-up and alerts.
3. Rate limits and fair use
We set rate limits and quotas to keep the service reliable. They’re published in the docs and may differ by plan. Don’t try to get around them, for example with multiple accounts. We may throttle traffic that threatens the service and will tell you if we do.
4. Sending messages
The Messaging API and Reach send email, SMS and WhatsApp on your behalf. You’re the sender. You must follow the Acceptable Use Policy, including consent, opt-out and sender identification rules, and the rules of each channel and country. In Nigeria, SMS uses NCC-registered sender IDs and respects Do-Not-Disturb. We may hold, delay or block messages that appear to break these rules, and suspend sending if complaint or bounce rates are too high.
5. What you build
5.1 You own your apps and content. You’re responsible for them, for your own users, and for your own terms and privacy notice to them.
5.2 Don’t imply that DUMO endorses your app. You may say your app is “built on DUMO” following our brand guidelines.
5.3 Don’t use the Developer Services to build a product that replicates DUMO as a whole or resells raw access to our APIs without our written agreement.
6. Changes to the APIs
6.1 We version our APIs. We’ll give at least 90 days’ notice before a breaking change to a generally available API, unless a change is needed sooner for security or legal reasons.
6.2 Beta APIs may change or be removed without notice and aren’t covered by any service level.
7. Webhooks and data
Verify webhook signatures and use HTTPS endpoints. Data you receive through the APIs about your customers is your responsibility as controller; protect it as required by law and the Data Processing Addendum.
8. Open-source components
SDKs and samples may include open-source software under its own licence, which governs that component.
9. Suspension
We may suspend a key or project that creates a security risk, breaks these terms or harms other customers, with notice where reasonable. Sections 14 to 19 of the Terms of Service apply.
Questions about this page? Email [email protected].

