Navigation
Authentication Endpoints Account Info Service List Place Order Get Order Status WebX REST API Order Statuses Error Handling Rate Limiting

API Documentation

DhruFusion V6.1 Compatible API for IMEI, Server, and Remote unlock services.

Authentication

All API requests require authentication. Two methods are supported:

Method 1: DhruFusion Standard (POST parameters)
POST https://imei-unlock.net/api/index.php
Content-Type: application/x-www-form-urlencoded

username=your@email.com
&apiaccesskey=YOUR_API_KEY
&action=accountinfo
Method 2: WebX REST (Auth-Key header)
GET https://imei-unlock.net/api/account
Auth-Key: YOUR_API_KEY
API Key: Generate your API key in Settings > API. Your IP will be auto-locked on first connection for security.

DhruFusion API Endpoints

Base URL: https://imei-unlock.net/api/index.php

Alternative URLs: https://imei-unlock.net/api or https://imei-unlock.net/dhru

All requests use POST with form-encoded parameters.

accountinfo

Get account balance and information.

Request
POST /api/index.php
username=your@email.com
&apiaccesskey=YOUR_API_KEY
&action=accountinfo
Response
{
  "SUCCESS": [{
    "MESSAGE": "Account info retrieved",
    "balance": "125.5000",
    "currency": "USD",
    "email": "your@email.com",
    "username": "your_username"
  }]
}

imeiservicelist

Get all available services (IMEI, Server, and Remote) grouped by category.

Request
POST /api/index.php
username=your@email.com
&apiaccesskey=YOUR_API_KEY
&action=imeiservicelist
Response
{
  "SUCCESS": [{
    "MESSAGE": "Service list retrieved",
    "LIST": [
      {
        "ID": 1,
        "SERVICENAME": "Samsung Galaxy Unlock",
        "GROUP": "Samsung",
        "GROUPTYPE": "IMEI",
        "PRICE": "5.00",
        "TIME": "1-24 hours",
        "INFO": "Supports all Samsung models"
      }
    ]
  }]
}
Type-specific lists: Use getimeiservices, serverservicelist, or fileservicelist for filtered lists.

placeimeiorder

Place an order. Auto-detects service type (IMEI, Server, or Remote) from the service ID.

Request
POST /api/index.php
username=your@email.com
&apiaccesskey=YOUR_API_KEY
&action=placeimeiorder
¶meters=BASE64_JSON
Parameters (base64-encoded JSON)
FieldTypeRequiredDescription
IDintYesService ID
IMEIstringYes*IMEI number (for IMEI services)
USERNAMEstringYes*Username/Account (for Server services)
QUANTITYintNoQuantity (for Server services, default: 1)

* Required field depends on service type.

Example (IMEI)
// Parameters JSON before base64:
{"ID": 1, "IMEI": "353272079261960"}

// Full request:
username=test@example.com
&apiaccesskey=abc123
&action=placeimeiorder
¶meters=eyJJRCI6IDEsICJJTUVJIjogIjM1MzI3MjA3OTI2MTk2MCJ9
Response
{
  "SUCCESS": [{
    "MESSAGE": "Order placed successfully",
    "REFERENCEID": "12345"
  }]
}

getimeiorder

Get order status and response. Auto-detects order type.

Request
POST /api/index.php
username=your@email.com
&apiaccesskey=YOUR_API_KEY
&action=getimeiorder
¶meters=BASE64_JSON
Parameters
{"ID": 12345}  // Order reference ID
Response
{
  "SUCCESS": [{
    "MESSAGE": "Order status retrieved",
    "ID": 12345,
    "STATUS": 4,
    "STATUSMSG": "Success",
    "CODE": "Unlock code: 12345678",
    "SERVICENAME": "Samsung Galaxy Unlock",
    "IMEI": "353272079261960"
  }]
}

WebX REST API

RESTful API with Auth-Key header authentication.

MethodEndpointDescription
GET/api/accountAccount info
GET/api/imei-servicesList IMEI services
GET/api/server-servicesList Server services
GET/api/file-servicesList File/Remote services
GET/api/imei-services/{id}Service details
POST/api/imei-ordersPlace IMEI order
POST/api/server-ordersPlace Server order
POST/api/file-ordersPlace File/Remote order
GET/api/imei-orders/{id}Get IMEI order status
GET/api/server-orders/{id}Get Server order status
GET/api/file-orders/{id}Get File order status

Order Statuses

CodeStatusDescription
0New / WaitingOrder received, awaiting processing
1In ProcessOrder sent to supplier, processing
2CancelledOrder cancelled (refunded)
3RejectedOrder rejected by supplier (refunded)
4SuccessOrder completed, code/response available

Error Handling

Errors are returned in this format:

{
  "ERROR": [{
    "MESSAGE": "Authentication failed: Invalid username or API key"
  }]
}
Common Errors
ErrorCause
Authentication requiredMissing username or apiaccesskey
Authentication failedInvalid credentials
API access is disabledEnable API in Settings > API
IP not authorizedReset IP lock in Settings > API
Invalid ActionUnknown action parameter
Invalid serviceService ID not found or inactive
Insufficient balanceNot enough credits

Rate Limiting

API requests are limited to:

  • 60 requests/minute per IP address
  • 120 requests/minute per API user

Rate limit headers are included in every response:

X-RateLimit-Limit: 120
X-RateLimit-Remaining: 115
Retry-After: 60  (only on 429)

When rate limited, you will receive a 429 Too Many Requests response.