Verify supplier API key binding

First integration call — verify key maps to correct supplier entity.

Why this method exists

First integration call — verify key maps to correct supplier entity.

When to use

Post key issuance smoke test; daily health cron.

Endpoint

POST /v1/supplier/profile/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:codes:read

Request example

{
  "meta": { "requestId": "optional-uuid" },
  "data": {}
}

Response example

{
  "success": true,
  "data": {
    "supplierId": "c219ef09-ae2f-4d08-af11-7cd51006fae4",
    "name": "Промомед",
    "legalName": "АО Промомед",
    "inn": "7701234567",
    "isActive": true,
    "defaultImportMaskId": "mask-uuid",
    "contactEmail": "integration@promomed.ru"
  }
}

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