Leads

leads/addAdd a lead#

Creates a lead (for a webmaster on one of their flows, for an agency directly on the offer). The lead is created if these conditions are met:

• Sending leads through the API is allowed for your account, otherwise the response is access.
• Affiliate only: the flow parameter holds your own flow, otherwise the response is noflow or badflow.
• The offer is available to you and accepts leads through the API, otherwise the response is no-api or traffic.
• offer and phone are passed.

You can pass the data in the query string, in a POST form, or in a JSON body with the Content-Type: application/json header. POST is recommended. If the JSON body is broken, the platform does not notice it and responds as if there were no data, usually with the noflow error. Parameters that are not in the table are ignored.

Field names are case-insensitive: Phone and phone are the same. Many fields are accepted under several names (the “Synonyms” column), so forms built for other systems connect without rewriting.

Repeating the request creates another lead unless the network turned on duplicate protection. If the connection broke while sending, do not repeat the request blindly. First look for the lead in leads/list by your subid.

Parameters

Parameters come in blocks: first the main ones, then tags, address, order contents and additional parameters. Offers with goods and cash on delivery need the address and the order contents.

Tags. The traffic source and your own lead identifiers.

Address. The customer's delivery address.

Order contents. Goods, prices and delivery cost.

Additional parameters. Placement, device, goal and custom order fields.

Request

https://lk.dalead.pro/api/leads/add.json?id={token}&offer=19&flow=63&phone=79001234567&name=Whiskers%20Pawson&email=whiskers%40meow.pro&country=ru&ip=203.0.113.42&ua=Mozilla%2F5.0%20%28iPhone%3B%20CPU%20iPhone%20OS%2017_5%20like%20Mac%20OS%20X%29&utm_source=facebook&utm_campaign=cathulhu-ru-01&subid=purr-42&comment=Call%20after%2018%3A00

curl 'https://lk.dalead.pro/api/leads/add.json?id={token}' \
  --data-urlencode 'offer=19' \
  --data-urlencode 'flow=63' \
  --data-urlencode 'phone=79001234567' \
  --data-urlencode 'name=Whiskers Pawson' \
  --data-urlencode 'email=whiskers@meow.pro' \
  --data-urlencode 'country=ru' \
  --data-urlencode 'ip=203.0.113.42' \
  --data-urlencode 'ua=Mozilla/5.0 (iPhone; CPU iPhone OS 17_5 like Mac OS X)' \
  --data-urlencode 'utm_source=facebook' \
  --data-urlencode 'utm_campaign=cathulhu-ru-01' \
  --data-urlencode 'subid=purr-42' \
  --data-urlencode 'comment=Call after 18:00'

// Lead from a landing form: customer and traffic data
$url  = 'https://lk.dalead.pro/api/leads/add.json?id={token}';
$data = [
    'offer' => 19,
    'flow' => 63,
    'phone' => $_POST['phone'],
    'name' => $_POST['name'],
    'email' => $_POST['email'],
    'country' => 'ru',
    'ip' => $_SERVER['REMOTE_ADDR'],
    'ua' => $_SERVER['HTTP_USER_AGENT'],
    'utm_source' => 'facebook',
    'utm_campaign' => 'cathulhu-ru-01',
    'subid' => 'purr-42',
    'comment' => 'Call after 18:00',
];
$ch = curl_init( $url );
curl_setopt_array( $ch, [
    CURLOPT_POST           => true,
    CURLOPT_POSTFIELDS     => http_build_query( $data ),
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_TIMEOUT        => 30,
]);
$r = json_decode( curl_exec( $ch ), true );
curl_close( $ch );
if ( isset( $r['error'] ) ) error_log( 'API error: ' . $r['error'] );

curl 'https://lk.dalead.pro/api/leads/add.json?id={token}' \
  -H 'Content-Type: application/json' \
  --data-raw '{"offer": 31, "flow": 63, "phone": "79001234568", "name": "Mittens Fluffy", "country": "ru", "ip": "203.0.113.42", "index": "127000", "city": "Moscow", "addr": "Meow street, 7-1", "items": [{"id": 1, "count": 2, "price": 1990}, {"id": 3, "count": 1, "price": 990}], "subid": "purr-43"}'

// Lead with goods and address (JSON body)
$url  = 'https://lk.dalead.pro/api/leads/add.json?id={token}';
$data = [
    'offer' => 31,
    'flow' => 63,
    'phone' => '79001234568',
    'name' => 'Mittens Fluffy',
    'country' => 'ru',
    'ip' => '203.0.113.42',
    'index' => '127000',
    'city' => 'Moscow',
    'addr' => 'Meow street, 7-1',
    'items' => [
        [
            'id' => 1,
            'count' => 2,
            'price' => 1990,
        ],
        [
            'id' => 3,
            'count' => 1,
            'price' => 990,
        ],
    ],
    'subid' => 'purr-43',
];
$ch = curl_init( $url );
curl_setopt_array( $ch, [
    CURLOPT_POST           => true,
    CURLOPT_POSTFIELDS     => json_encode( $data ),
    CURLOPT_HTTPHEADER     => [ 'Content-Type: application/json' ],
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_TIMEOUT        => 30,
]);
$r = json_decode( curl_exec( $ch ), true );
curl_close( $ch );
if ( isset( $r['error'] ) ) error_log( 'API error: ' . $r['error'] );

Response

A successful response means the platform recorded the lead. leads/list shows what happens to it next.

{
  "status": "ok",
  "id": 950084,
  "pin": 892529
}

{
  "status": "error",
  "error": "data",
  "bad": [
    "phone"
  ]
}

{
  "status": "error",
  "error": "badflow"
}

{
  "status": "error",
  "error": "traffic",
  "info": "offer"
}

Response fields.

Errors

Errors are listed in check order. The first ones come before the lead is created, the rest during creation.

An error does not always mean there is no lead. A duplicate caught before recording and the exto error return the id of the original order. Also, the advertiser can reject a lead right after it is recorded. Then an error comes (data with info: trash, duplicate, inactive, failed, and ban with GEO or language), but the response holds the id and pin of the new lead, and leads/list shows it with a decline phase (cancel or trash). If a response with an error has a pin, the id is a new lead. If there is no pin, the id (when there is one) is the original order.

The common errors key and ban (the token did not match, the account is blocked) come before the function. They are explained in the General API rules. It is easy to tell an account block from a refusal to accept a lead: a block has no info field, and a rejected lead always has it (table below).

info details

The info field gives details for the traffic and ban errors.

info values.

leads/listCheck lead statuses#

Returns your leads with their statuses. It returns all of them, not only those sent through the API, so it includes both the leads that came through flow URLs and the ones you sent from the cabinet. The request must contain at least one filter, otherwise the function responds with the no-param error.

The function is meant for spot checks, not for constant polling. To learn about a status change at once, set up postbacks, and the platform reports the change itself.

Parameters

All filters are combined with AND, so a lead must match every one. Every filter except the dates and the status accepts several values, and a lead matches if it has any of them. Pass them separated by commas (ids=1,2,3) or as an array (ids[]=1&ids[]=2). Text values are compared in full and case-sensitively, and a search by part of a value is not supported. Spaces at the edges are dropped. Unlike leads/add, parameter names here must be written exactly as in the table: UTM_SOURCE and the short utms do not count as a filter.

The output is not paged and does not accept limit and offset. The function returns all matching leads at once, but no more than 10,000 rows. If there may be more leads, split the selection by dates, for example one day at a time: from and to with the same date. The total field in the response is the number of rows in data, so a value of 10000 means the selection was cut off and you must narrow it.

Write dates in full. A wrong date is not an error, but the period comes out wrong: for example, from=2026-10 instead of the start of the month gives the last day of the previous one. An empty value (ids=) also counts as a filter, not as the absence of one. In numeric filters it turns into 0, like a non-numeric value. ids= and offer= find nothing, while site= and space= find leads without a landing or prelanding. In text filters (subid, utm_*, domain, customer, uid, src) an empty value means an empty tag. It finds the leads where the tag is not filled in.

Request

https://lk.dalead.pro/api/leads/list.json?id={token}&ids=950084

curl 'https://lk.dalead.pro/api/leads/list.json?id={token}' \
  --data-urlencode 'ids=950084'

// Lead by its number
$url  = 'https://lk.dalead.pro/api/leads/list.json?id={token}';
$data = [
    'ids' => 950084,
];
$ch = curl_init( $url );
curl_setopt_array( $ch, [
    CURLOPT_POST           => true,
    CURLOPT_POSTFIELDS     => http_build_query( $data ),
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_TIMEOUT        => 30,
]);
$r = json_decode( curl_exec( $ch ), true );
curl_close( $ch );
if ( isset( $r['error'] ) ) error_log( 'API error: ' . $r['error'] );

https://lk.dalead.pro/api/leads/list.json?id={token}&subid=purr-42

curl 'https://lk.dalead.pro/api/leads/list.json?id={token}' \
  --data-urlencode 'subid=purr-42'

// Leads by your own tag
$url  = 'https://lk.dalead.pro/api/leads/list.json?id={token}';
$data = [
    'subid' => 'purr-42',
];
$ch = curl_init( $url );
curl_setopt_array( $ch, [
    CURLOPT_POST           => true,
    CURLOPT_POSTFIELDS     => http_build_query( $data ),
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_TIMEOUT        => 30,
]);
$r = json_decode( curl_exec( $ch ), true );
curl_close( $ch );
if ( isset( $r['error'] ) ) error_log( 'API error: ' . $r['error'] );

https://lk.dalead.pro/api/leads/list.json?id={token}&from=2026-10-01&to=2026-10-31&status=approve

curl 'https://lk.dalead.pro/api/leads/list.json?id={token}' \
  --data-urlencode 'from=2026-10-01' \
  --data-urlencode 'to=2026-10-31' \
  --data-urlencode 'status=approve'

// Approved leads for the month
$url  = 'https://lk.dalead.pro/api/leads/list.json?id={token}';
$data = [
    'from' => '2026-10-01',
    'to' => '2026-10-31',
    'status' => 'approve',
];
$ch = curl_init( $url );
curl_setopt_array( $ch, [
    CURLOPT_POST           => true,
    CURLOPT_POSTFIELDS     => http_build_query( $data ),
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_TIMEOUT        => 30,
]);
$r = json_decode( curl_exec( $ch ), true );
curl_close( $ch );
if ( isset( $r['error'] ) ) error_log( 'API error: ' . $r['error'] );

Response

{
  "status": "ok",
  "total": 1,
  "data": [
    {
      "id": 950084,
      "time": 1793389833,
      "status": {
        "phase": 1,
        "stage": "wait",
        "hold": 0,
        "goal": false,
        "ftd": false,
        "deposited": false,
        "crm": 2,
        "reason": 0
      },
      "payment": {
        "amount": 550,
        "currency": "rub",
        "convert": 550
      },
      "offer": {
        "id": 19,
        "name": "Bed linen",
        "flow": 63,
        "site": 0,
        "space": 0,
        "siteurl": false,
        "spaceurl": false
      },
      "tags": {
        "source": "facebook",
        "content": "",
        "campaign": "cathulhu-ru-01",
        "medium": "",
        "term": "",
        "domain": "",
        "customer": "",
        "adid": "",
        "uuid": "",
        "subid": "purr-42",
        "sub1": "",
        "sub2": "",
        "sub3": "",
        "sub4": "",
        "sub5": "",
        "click": "",
        "extu": "",
        "exts": ""
      },
      "info": {
        "country": "ru",
        "ip": "203.0.113.42",
        "ua": "Mozilla/5.0 (iPhone; CPU iPhone OS 17_5 like Mac OS X)",
        "comment": ""
      }
    }
  ]
}

{
  "status": "ok",
  "total": 0,
  "data": []
}

The response consists of the common fields (the result and the number of leads) and the data array of leads.

Response fields.

A row in data:

Lead row.

The status object:

The status object, main fields.

The payment object:

The payment object.

The offer object:

The offer object.

The tags object:

The tags object.

The info object:

The info object, main fields.

If the network connected you as an agency with extended statistics, the info object adds the customer data, the delivery address and the order contents to the four fields above:

The info object, additional fields.

An item in goods:

An element of the goods array.

Errors

The token errors (key, ban) come before the function: see the General errors.