Incoming batches for platform

Completed incoming metadata relevant to platform catalog.

Why this method exists

Completed incoming metadata relevant to platform catalog.

When to use

Campaign planning after supplier delivery.

Endpoint

POST /v1/platform/incoming/list

Authentication: X-Api-Key header (prefix bk_plt_). Do not send projectId or actor id in body — they come from the key.

Scope: platform:incoming:read

Request example

{
  "meta": { "requestId": "optional-uuid" },
  "data": { "page": 1, "pageSize": 50, "completedSince": "2026-07-01" }
}

Response example

{
  "success": true,
  "data": {
    "items": [
      {
        "incomingId": "f47ac10b-…",
        "supplierName": "Промомед",
        "documentDate": "2026-07-13",
        "insertedAvailable": 1480,
        "codesAvailableForPlatform": 1480,
        "completedAt": "2026-07-13T09:20:00Z"
      }
    ],
    "totalCount": 3
  }
}

Errors

UNAUTHORIZED / ACCESS_DENIED — access denied
VALIDATION_ERROR — invalid body
NOT_FOUND — resource not found
RATE_LIMIT_EXCEEDED (429) — rate limit

cURL

curl -X POST "https://api-external.promanta.ru/v1/platform/incoming/list" \
  -H "Content-Type: application/json" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -d '{"data": { "page": 1, "pageSize": 50, "completedSince": "2026-07-01" }}'