Incoming import status

Supplier checks import completion and row counters for ERP closure.

Why this method exists

Supplier checks import completion and row counters for ERP closure.

When to use

Poll every 10–30s after import.

Endpoint

POST /v1/supplier/incoming/get

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

Scope: supplier:incoming:read

Request example

{
  "meta": { "requestId": "optional-uuid" },
  "data": { "incomingId": "f47ac10b-…" }
}

Response example

{
  "success": true,
  "data": {
    "incomingId": "f47ac10b-…",
    "documentNumber": "PM-2026-07-001",
    "status": "completed",
    "counters": {
      "totalRows": 1500,
      "insertedAvailable": 1480,
      "duplicateRows": 10,
      "errorRows": 2
    },
    "completedAt": "2026-07-13T09:25:00Z"
  }
}

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/supplier/incoming/get" \
  -H "Content-Type: application/json" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -d '{"data": { "incomingId": "f47ac10b-…" }}'