If you sell software or services to businesses, the Partner API lets your own system create, run and bill a QuickGrow account for each of your customers — twenty-four calls covering the whole life of that account. You keep the customer. We carry the email, SMS and WhatsApp.
Carrying email, SMS and WhatsApp yourself means operator contracts, a sender-name approval, a WhatsApp Business account, delivery reporting, and somebody on call when a send fails. This page is for companies who would rather sell that than build it.
You already sell a system — a school platform, a clinic booking tool, a delivery app — and customers keep asking it to send reminders and codes. Your code creates a QuickGrow account per customer and sends through it. Whether they ever log in is your decision, not ours.
You sell and support software to a book of businesses. Add messaging to what you sell, onboard a customer with one call instead of a form, and read back a ledger line per customer so the monthly invoice is a query rather than an afternoon.
There is no self-serve partner tier. We create the partner record, agree the scopes your key carries, and lock it to the server addresses you call from. That conversation starts on the contact page.
Not quite you? If you run the campaigns for your clients yourself, the agency route fits better. If you only want to make the introduction, the referral programme pays for that.
The Partner API is server-to-server: your backend calls ours, using your own id for each customer. Nothing in this loop needs a person in a browser.
It carries only the scopes you ask for — creating accounts, reading, sending, billing — and can be restricted to your own server addresses. Every request is signed and stamped with the time; one more than five minutes old is refused, so a copied request is dead.
One call, carrying your own id for that customer, creates the account, its owner login and a key for your code to send with. Call it again with the same id and you get the same account back — a retry never leaves you with two.
One-off sends for codes, receipts and alerts, or a batch to a list of recipients or a saved segment, with a cost estimate before you commit. Every message comes back with a state and, when it fails, a reason.
Read top-ups, spend and balance per customer since any date you choose. Suspend an account and its keys stop working; resume and they come back; schedule an erasure of the data when the relationship ends.
One provisioning call builds the whole thing: the account, its owner user, a starter wallet and an API key for your code. Inside it is the same product this site sells — contacts, campaigns, a shared inbox, reports — so if you ever do hand the login over, there is something worth logging into.
This is the whole Partner API as it ships today. Everything below is reachable from your own backend with a partner key, and none of it needs one of your customers to do anything first.
Worth settling before you build. QuickGrow is a co-branded platform rather than a white-label one: what your customer’s own recipients see is your customer’s brand, and the product your customer would log into is still ours.
| Whose name appears | Who sets it | |
|---|---|---|
| The email, SMS and WhatsApp their customers receive | Your customer’s | Set per account, by you or by them |
| The account name, logo and sender details inside the product | Your customer’s | You, at set-up or on any later update call |
| The dashboard and login page, if your customer ever opens one | QuickGrow’s | Not re-skinned today |
| A “Powered by QuickGrow” logo and channel icons the API hands you | QuickGrow’s | Ours, for you to place inside your own product |
| Your product, your support, your invoice | Yours | You — we are not in that conversation |
No, and it is worth being blunt about it. Messages go out under your customer’s own sender name, and the account carries their name and logo, so their recipients see them rather than us. But the QuickGrow dashboard is not re-skinned under your brand, and there is no switch that makes it so. What the Partner API does hand you is a “Powered by QuickGrow” logo and channel icons to place inside your own product. If a re-skinned dashboard is a hard requirement, tell us before you sign anything.
Every account belongs to exactly one partner, and that check runs before anything else. Ask for an account you do not own and the answer is “not found” — not an error that confirms it exists, and never somebody else’s data. On top of that, your key carries only the scopes you asked for, can be locked to your own server addresses, and every request must be signed and time-stamped.
It does not. Accounts are keyed on your own id for the customer, so a second call with the same id returns the account that already exists and does not mint a second key. The same holds for a batch send: repeat the same request key and you get the original batch back rather than sending twice.
Bring the shape of it — how many customers, which channels, and whether you want them paying us or you. We will tell you what your key needs to carry and what the terms look like.
CyberCraft BangladeshQuickGrow AIRun every channel from one platform. Bring your own SMTP, SMS gateway, and WhatsApp number — or use ours.
See pricing →