Webhook fallback for incoming.
Why this method exists
Webhook fallback for incoming.completed-style events.
When to use
No webhook or disaster replay.
Endpoint
POST /v1/platform/events/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:events:read
Request example
{
"meta": { "requestId": "optional-uuid" },
"data": { "since": "2026-07-13T00:00:00Z", "limit": 100 }
}
Response example
{
"success": true,
"data": {
"items": [
{
"eventId": "evt-uuid",
"eventType": "incoming.completed",
"occurredAt": "2026-07-13T09:20:00Z",
"data": {
"incomingId": "f47ac10b-…",
"supplierName": "Промомед",
"insertedAvailable": 1500
}
}
],
"hasMore": false
}
}
Errors
UNAUTHORIZED/ACCESS_DENIED— access deniedVALIDATION_ERROR— invalid bodyNOT_FOUND— resource not foundRATE_LIMIT_EXCEEDED(429) — rate limit
cURL
curl -X POST "https://api-external.promanta.ru/v1/platform/events/list" \
-H "Content-Type: application/json" \
-H "X-Api-Key: YOUR_API_KEY" \
-d '{"data": { "since": "2026-07-13T00:00:00Z", "limit": 100 }}'