Bulk redeem promo codes

Platform reports customer activation: realized → redeemed.

Why this method exists

Platform reports customer activation: realized → redeemed.

When to use

Nightly billing sync; own realized codes only.

Endpoint

POST /v1/platform/usage/report-bulk

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

Scope: platform:usage:write

Idempotency-Key: required (header). Retries with the same key return cached response.

Request example

{
  "meta": { "requestId": "optional-uuid" },
  "data": { "items": [{ "codeId": "code-uuid", "redeemedAt": "2026-07-13T14:30:00Z", "externalRef": "act-112233" }] }
}

Response example

{
  "success": true,
  "data": {
    "summary": { "total": 1, "accepted": 1, "rejected": 0 },
    "results": [{ "codeId": "code-uuid", "success": true, "newStatus": "redeemed" }]
  }
}

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/usage/report-bulk" \
  -H "Content-Type: application/json" \
  -H "X-Api-Key: YOUR_API_KEY" \
  -H "Idempotency-Key: unique-key-001" \
  -d '{"data": { "items": [{ "codeId": "code-uuid", "redeemedAt": "2026-07-13T14:30:00Z", "externalRef": "act-112233" }] }}'