User API
Authorize devices from your own software
One HTTPS call with your username and password: send the device's request, get the signature back in the same answer. Same credits and prices as in the app.
https://shadowauthtool.com/api/v1/apiservice.phpPOST · form fields or JSONYour username and password1Before you start
| You need | How to get it |
|---|---|
| An account | Register and confirm your email. The API uses the same username and password as the app. |
| Credits | Send your username to an official reseller. |
2One call
curl -X POST https://shadowauthtool.com/api/v1/apiservice.php \ -d username=your-username \ -d password=your-password \ -d serviceid=1 \ --data-urlencode configblob="<the request read from the device>"
{
"status": "success",
"message": "Authorized",
"data": "3A9F0C...",
"requestid": "c1a9...",
"price": 3.00,
"credits": 27.00
}data is the signature to send to the device. credits is your balance after this authorization.
| Field | Meaning |
|---|---|
username, password | Your account. |
serviceid | Which service (table below). |
configblob | The device's request (what to send). |
reference | Optional, recommended: your own order number. If your connection drops, send the same call with the same reference again: you get the first result back and pay only once. |
imei | Optional: the device's 15-digit IMEI. |
The call waits until the authorization is finished, usually a few seconds and at most 150 seconds. Set your HTTP timeout to at least 160 seconds.
3Services
| Service | serviceid |
|---|---|
| EDL Authorization (Qualcomm) | 1 |
| FRP Authorization | 2 |
| FDL Authorization | 4 |
| V5 Authorization (MediaTek) | 7 |
| V6 Authorization (MediaTek) | 8 |
| V6 New Authorization (MediaTek) | 11 (or 12) |
| UBL for inactive devices | 20 |
| India Instant UBL | 21 |
The ids up to 12 are the same as on other authorization servers, so a tool that already speaks that protocol only needs the new URL and your account. Your prices: action=services (section 6).
4What to send
| Service | configblob | data you get |
|---|---|---|
| EDL, FDL (1, 4) | The authorization request read from the device, as text. | Signature, hex |
| V5, V6 (7, 8) | The device's request, Base64. | Signature, hex |
| V6 New (11, 12) | The device token, Base64. Also send platformname and projectname, optionally authtier (single or dual). | Signature, hex |
| FRP (2) | Base64 of the JSON request from the device. | The server's answer, unchanged |
| UBL (20) | JSON with productName, token and sn_device from Fastboot. | Unlock data, hex |
| India UBL (21) | JSON with mn, sn, prd and devdata (the complete Fastboot token, never shortened with "..."). | Unlock data, Base64 |
The whole request may be at most 3,000 characters.
5Answers
Every answer is JSON with HTTP 200 and a status:
status | Meaning |
|---|---|
success | Done: data holds the signature. Credits have been charged. |
error | Not authorized: message says why, code is for your software. Failed authorizations cost nothing. |
pending | Not finished within 150 seconds. Ask again later with action=status and the requestid. |
{
"status": "error",
"code": "unsupported_device",
"message": "Device not supported. MDM, CN, Finance and FMI devices are not supported (except MTK V6 OLD).",
"requestid": "c1a9...",
"price": 3.00
}code | Cause and fix |
|---|---|
invalid_credentials | Wrong username or password. After 5 wrong passwords the account is locked for 15 minutes. |
email_not_verified | Confirm your email from the registration email first. |
insufficient_credits | Not enough credits. Top up through a reseller. |
invalid_service | Unknown serviceid. |
invalid_authorization_blob | configblob is missing or not in the format of section 4. |
unsupported_device | The device is not supported (flashing rules). |
all_servers_offline | All servers offline. Try again in a few minutes. No credits were charged. |
authorization_pending_limit | 3 of your requests are already running. Wait for one to finish. |
6Balance and status
Add action to the same call (with your username and password):
action | Returns |
|---|---|
balance | credits: what you can spend. |
services | services: each serviceid with its name and your price. |
status + requestid | The current answer for an earlier request, without waiting. |
curl -X POST https://shadowauthtool.com/api/v1/apiservice.php \
-d username=your-username -d password=your-password -d action=balance
{ "status": "success", "credits": 27.00 }7Limits
- 60 calls per minute from one IP address, at most 3 authorizations running at the same time.
- After 10 wrong passwords from one IP address the API answers HTTP 429 for 5 minutes.
- Administrator and reseller accounts cannot use this API; use a normal user account.
- Your password travels in every call: only send it to
https://shadowauthtool.com, never put it in public code, and change it if it leaks.
Questions: support. Include the requestid, never your password.