Admin API: conversions and postback

The API offers the same actions as the panel: conversion types, importing conversions from CSV and the event delivery log. Authorization is described on the Admin API: overview and authorization page, and the request, response and error format on the Request, response and error format page.

Methods in this group

If {id} in the address is not a UUID, the response is 400 with the bad_request code. With an inactive license, all methods in the group respond with 402 — see Expired license.

A campaign's log of accepted conversions is returned by GET /api/v1/campaigns/{id}/conversions — see Admin API: campaigns.

Receiving postbacks and leads

The /api/v1/postback, /api/v1/lead and /api/v1/lead-file addresses accept data without a token; they do not need the Api-Key header. Postback parameters, statuses, payout, txid and the source secret are described on the Incoming postback page, repeats and corrections on the Transaction ID, duplicates and corrections page, and receiving data from forms on the Receiving leads from forms page.

Conversion types

A type maps the status value from an affiliate network's postback to a tracker status. The mapping rules are on the Conversion types page.

Type object:

List types

GET /api/v1/conversion-types

Returns all of the team's types in order of creation. Token scope: full or reports:read. No parameters.

Response — code 200 and an array of type objects. If there are no types, an empty array [].

Create a type

POST /api/v1/conversion-types

Creates a conversion type. Token scope: full.

Response — code 201 and the created type object.

curl -X POST https://panel.example.com/api/v1/conversion-types \
  -H "Api-Key: <token>" \
  -H "Content-Type: application/json" \
  -d '{"name":"Deposit","status":"sale","params":"deposit,ftd","send_postback":true}'

Errors: 422, code validation, message name is required — there is no name field or the body is not a JSON object.

Edit a type

PUT /api/v1/conversion-types/{id}

Replaces the type's settings. Token scope: full.

The body fields are the same as on creation; name is required. Pass the whole object:

• omitted count_conv, count_revenue and send_postback become false;
• omitted params and color become an empty string;
• an omitted or empty status does not change.

Response — code 200 and the type object after the change.

Errors:

Delete a type

DELETE /api/v1/conversion-types/{id}

Deletes a type. Token scope: full. No request body.

Response — code 204 with no body. If there is no type with this ID — 404, code not_found. What happens to already accepted conversions is described in the Deleting and changing section.

Importing conversions from CSV

The import takes two requests: the check returns a token, and the import accepts the same data together with this token. The file format and the rules for each column are on the Conversion import from CSV page.

Body of both requests:

Response of both requests — code 200:

Check a CSV

POST /api/v1/conversion-import/preview

Checks the file and writes nothing. Token scope: full.

If valid is false, fix the rows with the error field and repeat the check. Row error messages are covered in the If something went wrong section.

curl -X POST https://panel.example.com/api/v1/conversion-import/preview \
  -H "Api-Key: <token>" \
  -H "Content-Type: application/json" \
  -d '{"csv":"sub_id,payout,tid,status\n1a2b3c4d5e6f,25.5,order-1001,sale\n","currency":"USD","notify":false}'

{
  "rows": [
    {"line": 2, "click_id": "1a2b3c4d5e6f", "payout": "25.5", "tid": "order-1001", "status": "sale"}
  ],
  "valid": true,
  "token": "1791021600.9f2c…",
  "applied": false,
  "notify": false
}

Errors:

Import a CSV

POST /api/v1/conversion-import/apply

Writes conversions from the checked file. Token scope: full.

Send the same csv, currency and notify as in the check, and add the token. It is valid for 15 minutes and fits only this data and only the user whose API token ran the check. If you changed even one field, check the file again.

Rows are processed by the same rules as an incoming postback. With applied: true, each row has a result:

• result with the value Принято (точный повтор не создаёт дубль) (accepted; an exact repeat does not create a duplicate) — the conversion was accepted;
• error with the value Не принято: HTTP <код>. Проверьте журнал postback; строку можно повторить с тем же tid. (not accepted: HTTP code; check the postback log; the row can be repeated with the same tid) — the row was not written; the other rows are not affected.

If valid is false during import, nothing is written: applied is false.

Errors — the same as for the check, plus two more:

Deliveries

A delivery task is writing an accepted conversion to the statistics, an outgoing S2S postback or a Facebook Conversions API event. What the states and results mean and when a retry is safe is described on the Event delivery log page.

Task object:

Latest deliveries

GET /api/v1/deliveries

Returns the team's last 200 tasks, newest first. Token scope: full. No parameters.

Response — code 200 and an array of task objects.

Search deliveries

GET /api/v1/deliveries/search

Searches tasks by click, period and filters. Token scope: full.

The period is no longer than 93 days. If click_id is passed without from and to, the search covers all time.

Response — code 200:

curl "https://panel.example.com/api/v1/deliveries/search?state=failed&kind=s2s&from=2026-10-01T00:00:00Z&to=2026-10-04T00:00:00Z&limit=50" \
  -H "Api-Key: <token>"

{
  "items": [
    {
      "held_for_license": false,
      "id": "0b7e4c19-6a2d-4f85-b3c1-8d9e0f1a2b3c",
      "campaign_id": "c41a9e07-52bd-4f13-8a60-9d7e6f5a4b3c",
      "click_id": "1a2b3c4d5e6f",
      "kind": "s2s",
      "destination": "source",
      "state": "failed",
      "attempts": 1,
      "result_code": "http_404",
      "created_at": "2026-10-03T14:22:05.418332Z",
      "updated_at": "2026-10-03T14:22:06.102778Z",
      "next_attempt_at": "2026-10-03T14:22:05.418332Z"
    }
  ],
  "next_cursor": ""
}

Errors — code 400, code is validation.

Retry a delivery

POST /api/v1/deliveries/{id}/retry

Puts the task back in the queue: state becomes pending, and sending happens immediately and in the same form. Token scope: full. The address contains the task id; there is no request body.

Only a task in the failed state can be retried. Tasks with result_code equal to invalid_url, blocked_address, invalid_payload or invalid_kind are not retried.

Response — code 200:

{"ok": true}

Errors: 404, code not_found — there is no task with this ID, it is not in the failed state, or it cannot be retried.