AUTHORIZED PARTNER INFRASTRUCTURE
External Reseller Network
Secure access for approved resellers to manage balance, API credentials and automated requests.
Mandatory two-factor authentication
Protect the account before the Owner can activate it.
Scan this QR with Google Authenticator, Microsoft Authenticator or another compatible app.
CHOOSE YOUR COMMERCIAL LEVEL
Partner plans
Professional reseller
Approximately 12% marginExact top-ups: USD 500, 600 or 700.
High-volume reseller
20% preferred marginExact top-ups: USD 800, 1000, 1500 or 2000.
An ELITE account cannot downgrade to PRO. Credit-package pricing is identical on both plans.
Fund your partner wallet
Arbitrary amounts and decimals are rejected by the API and PostgreSQL.
API credentials
Each secret is shown once. Store it in your server's secret manager, never in browser code.
Latest requests
API quick reference
Authorization: Bearer pk_live_...
POST https://partner-api.multiunlockmdm.com/api/v1/automation/licenses
{ "externalReference":"ORDER-1001", "productCode":"VIP_3M_1M", "username":"client", "email":"client@example.com" }
POST https://partner-api.multiunlockmdm.com/api/v1/automation/credits
{ "externalReference":"ORDER-1002", "packageCode":"CRD_20", "username":"client", "email":"client@example.com" }
License product codes:
GOLD_3M | VIP_3M_1M | GOLD_6M | VIP_6M_1M | GOLD_12M | VIP_12M_1M
Credit package codes:
CRD_10 | CRD_20 | CRD_30 | CRD_50
Accepted / queued response (HTTP 202):
{ "requestId":"uuid", "externalReference":"ORDER-1001", "status":"Queued" }
Destination rejected (HTTP 409):
{ "code":"LICENSE_ALREADY_ACTIVE", "message":"The account already has an active license..." }
Check a request:
GET /api/v1/automation/requests/{requestId}
Possible statuses: WaitingFunds, Queued, Processing, Done, Failed, Cancelled.Account validation: username and email must exactly match an active User account with verified email. License requests are rejected when the account already has an active license or its license is suspended. No balance is consumed when the core rejects the request. Product codes and response schemas are safe to document; never publish a real API key, session token or internal bridge secret.