Community
Building on Digimart, together
Digimart's community is still small and mostly runs through direct support. We would rather tell you that plainly than point you at a channel that nobody answers.
Getting help
These two channels are staffed and real. Everything technical goes to email.
Developer support
General inquiries and every technical question, integration problems, error codes, revenue share, app approval status, marketing approval.
support@digimart.storeBy phone
For anything urgent or commercial. Technical debugging is far easier over email, where you can paste a request ID.
+8801764987009Get a faster answer
How to ask a question that gets solved
Support cannot look up a transaction they cannot identify. Including these six things turns a multi-day thread into a single reply.
Your requestId
The 15-digit ID from the failing call. This is the single most useful thing you can send.
The exact status code
E1002, E3009, and so on, not "it failed".
Your App ID
The applicationId of the app in the portal. This one is required, it is how support finds your application. You do not need to send your API Key, and never the API Secret.
The masked subscriber number
The masked MSISDN (the subscriberId Digimart returned) is safe to send in a ticket and helps trace the subscriber. Send the masked value, not the customer's real number.
The timestamp
The requestTime you sent, so the call can be located in the logs.
What you expected instead
One sentence. It is often where the actual misunderstanding shows up.
Never share these
- Your API Secret, with anyone, ever.
- A customer's real, unmasked mobile number. Send the masked subscriberId instead, that is what support works with.
- An OTP, even an expired one.
- Screenshots of your portal with credentials visible.
Follow along
Where to find Digimart
Announcements and product news go out on Facebook and LinkedIn. WhatsApp and email reach a person, and anything technical is still best written up as an email.
Short of an idea? Borrow one of ours
The idea bank inside Use cases is a searchable, categorised collection of things worth building on mobile-balance charging. Every entry spells out who it serves, the problem it solves and how Digimart fits. Take any of them and make it yours.
Help improve these docs
Found something wrong or missing?
Parts of the API reference on this site are marked as Draft. Those are reconstructions of the documented flow, not text copied from an official specification, and the fastest way they get corrected is a developer who hit the real behaviour telling us what it actually does.
If a parameter behaves differently, an error code means something else, or a step is missing, tell us. It helps everyone who reads this page after you.