The unlocking trade standardised on the DHRU Fusion protocol years ago. Supplier panels expose it. Desktop tools speak it. A store that cannot import a Fusion service list, or cannot answer Fusion on the way out, forces everyone to start again.
GSMSS implements Fusion on both sides. Inbound: you add a Fusion (or native GSMSS) connection, import the catalogue, set markup, and orders go out automatically. Outbound: every customer can have an API key and place IMEI and server orders against /api/index.php with the actions they already know, plus a modern REST API and a public documentation page you can hand them.
Supplier side
- Add a Fusion connection with the username and API key you already have.
- Import the whole service list. Map each row to your price and group.
- Costs and remote prices re-sync about every three hours.
- No monthly cap on automated orders on any plan.
- A native GSMSS API connector sits next to Fusion for first-party routes.
Reseller side
Your store answers the standard DHRU Fusion API actions on /api/index.php, so existing reseller tools only change the host name:
| Fusion action | What it does |
|---|---|
accountinfo | Balance, currency and account name |
imeiservicelist | Your IMEI services with the reseller's own price |
placeimeiorder | Place an IMEI order, paid from the wallet |
getimeiorder | Status and result of one order |
getimeiorderbulk | Status of many orders in one call |
getserverservicelist | Your server services and prices |
Server orders go through the REST API: POST /api/v1/orders with type=server. The REST API also lists services, orders and wallet transactions in JSON, for anyone building a new integration rather than reusing an old one.
What a Fusion order looks like
POST https://your-store.com/api/index.php
username=reseller
apiaccesskey=YOUR_KEY
action=placeimeiorder
service=42
imei=352099001761481
→ {"SUCCESS":[{"MESSAGE":"Order placed successfully.",
"LIST":{"REFERENCEID":100245,"ORDERNO":"IMEI-100245","STATUS":"PENDING"}}]}Replies use the familiar Fusion SUCCESS / ERROR envelope, which is why resellers do not have to rewrite anything when you move. Instant services come back with the result in the same reply.
Why this matters when you leave another panel
A migration that keeps Fusion on both sides is a DNS and credential change, not a rebuild. That is the difference between resellers staying and resellers asking for a refund of their integration time. Pair this with the DHRU alternative page if you are comparing panels, or the IMEI store page if you are starting fresh.
Questions
Do I need a Fusion-compatible supplier? ＋
It is the fastest path. You can also use the native GSMSS connector or a custom JSON / URL lookup provider.
Will desktop reseller tools keep working? ＋
If they already speak Fusion, yes. Point them at your store's /api/index.php.
Is there a request limit? ＋
We do not cap automated supplier orders by the month. Normal rate limits still protect login and the public API from abuse.
Where is the documentation? ＋
Each store ships a public API docs page. Resellers also see their key under Dashboard → API Access.
Can resellers place server orders over Fusion? ＋
Server services are listed over Fusion (getserverservicelist). Server orders are placed with the REST API: POST /api/v1/orders with type=server.
Ready to run this on your domain?
Every plan includes hosting, SSL, updates and a free migration. Cancel anytime.
See pricing