Admin API: logs and diagnostics

The API offers the same data as the Logs section of the panel and the System status page. All ten methods require a token with Full access («Полный доступ») (full): with a different access type you get 403 token_scope. With an inactive license, the methods respond with 402 — see Expired license. Authorization is described on the Admin API: overview and authorization page, and the response format and common error codes on the Request, response and error format page.

Clicks

Search clicks

GET /api/v1/logs/clicks

Returns clicks for a period. You can select clicks by an exact IP, subid or external_id. The search rules are the same as on the Clicks and leads tab.

Response — code 200:

Example request:

curl "https://panel.example.com/api/v1/logs/clicks?from=2026-10-01T00:00:00Z&to=2026-10-04T00:00:00Z&field=ip&value=203.0.113.10&limit=50" \
  -H "Api-Key: <token>"

Example response, some click fields omitted:

{
  "items": [
    {
      "subid": "k3x9m2q7c1ab",
      "ts": "2026-10-03T14:22:05.418Z",
      "ip": "203.0.113.10",
      "campaign_id": "c41a9e07-52bd-4f13-8a60-9d7e6f5a4b3c",
      "stream_id": "5e2d7a10-8c4b-4f6e-b1a9-0d3c2b1a4f5e",
      "country": "PL",
      "is_bot": false,
      "is_unique": true,
      "tokens": {"external_id": "ext-448812"}
    }
  ],
  "next_cursor": "",
  "names": {"c41a9e07-52bd-4f13-8a60-9d7e6f5a4b3c": "FB PL Nutra"}
}

Errors:

Click card

GET /api/v1/logs/clicks/{id}

Returns a click, its landing page clicks and its conversions — the data of the click card. The click is searched across the whole stored history; no period is needed.

Response — code 200:

The response does not include the event delivery history: it is returned by GET /api/v1/deliveries/search with the click_id parameter — see Admin API: conversions and postback. Lead data is returned by GET /api/v1/reports/click-lead — see Admin API: reports.

Errors:

Action log

GET /api/v1/logs/audit

Returns entries of the user action log, newest first.

Response — code 200: an object with the fields items, total (the number of entries matching the filter), page and limit.

Example request — failed campaign changes over one day:

curl "https://panel.example.com/api/v1/logs/audit?resource=campaigns&outcome=error&from=2026-10-03T00:00:00Z&to=2026-10-04T00:00:00Z&limit=50" \
  -H "Api-Key: <token>"

Errors — code 422, code validation:

Stream logs

Four logs: system — the system log, postback — incoming postbacks, s2s — outgoing S2S, traffic — the traffic log. What goes into them is described on the System log, postbacks and traffic log page. Each log keeps the 2000 latest entries; the logs are shared by the whole installation.

Read a log

GET /api/v1/logs/{stream}

Returns the log's entries, newest first.

Response — code 200 and an array of entries. If there are no entries, [] is returned.

Error: 404, code not_found, message неизвестный поток логов (unknown log stream) — the stream value is not from the list.

Clear a log

DELETE /api/v1/logs/{stream}

Deletes all entries of the log for the whole installation. The stream path parameter is the same as for reading.

Response — code 204 with no body.

Check whether the traffic log is on

GET /api/v1/logs/traffic-enabled

No parameters. Response — code 200:

{"enabled": false}

Turn the traffic log on or off

PUT /api/v1/logs/traffic-enabled

Switches recording of the traffic log — the same as the Log («Логировать») toggle on the Traffic («Трафик») tab.

Response — code 200 and the {"enabled": true} object with the new value.

Error: 400, code bad_request, message invalid json — the body was not parsed.

Diagnostics

Queue state

GET /api/v1/queue-health

Returns the click intake queue and unfinished delivery tasks — the data of the Queue state tab.

No parameters. Response — code 200:

Error: 503, code unavailable — the delivery queue could not be read. The response has the Retry-After: 5 header: repeat the request after 5 seconds.

System status

GET /api/v1/system-health

Returns the data of the System status page: build, services, background tasks and exports.

No parameters. The method responds with code 200 even when a service is unavailable: check the state field.

Task names in workers: report_exports, deliveries, target-monitor, retention, domain-checks. stale is true if the last heartbeat is older than 3 minutes.

Traffic settings rollout

GET /api/v1/runtime-config

Shows whether changes to campaigns, streams and domains have reached the traffic processing servers. How to read the statuses is described on the Traffic processing servers page.

No parameters. Response — code 200:

Server fields in nodes: node — name, revision — the confirmed version, checked_at — the last heartbeat (the field is absent for a server that has never responded), expected — whether it is in the expected list, stale — no fresh heartbeat, instances — how many running servers reported this name, state — the state:

Error: 503, code config_unavailable, message Состояние конфигурации недоступно (configuration state unavailable).