API & settings

A new key stops the old one immediately, in your integrations too.

Send your key in the X-API-Key header (recommended) or as the key parameter.

Successful response:

{
  "status": "success",
  "orderId": 6320908,
  "identifier": "353456789012345",
  "service": 1,
  "priceCharged": 0.18,
  "balance": 1204.33,
  "exec_ms": 1412,
  "message": { "...": "service specific result", "htmlResponse": "..." }
}

Error response (HTTP status explains the cause: 400, 401, 402, 404, 422, 429, 503):

{ "status": "error", "message": "Insufficient balance" }

In your Dhru Fusion admin, add a new API connection (supplier) of type Dhru Fusion with these details, then sync the IMEI service list:

How Dhru orders are processed

• Orders are accepted instantly and queued; your panel shows them as In process until the result is ready (usually within a few minutes).
• Orders are sent to the source one after another, at a controlled pace, so large bulks are handled safely. Up to orders per bulk request and waiting at a time.
• The price is reserved when the order is placed and charged only when the result is delivered. Rejected orders are never charged; the reservation is released.
• The same IMEI sent twice for the same service while the first order is still waiting returns the same order reference.