---
title: "GLEIF Level 1 LEI linkage for a Swiss UID (body-based)"
method: POST
path: "/api/v1/lei-lookup"
---

# GLEIF Level 1 LEI linkage for a Swiss UID (body-based)

`POST /api/v1/lei-lookup`

## Request

- Base URL: `https://bumit.ai`
- URL: `https://bumit.ai/api/v1/lei-lookup`
- Auth: none required

Replacement for the deprecated GET /api/v1/company/{uid}/lei. Reads locally stored GLEIF data only; GLEIF is never contacted.

The UID is supplied in the JSON request body and never in the URL. Only the listed fields are accepted; unknown fields are rejected (400). No login, no API key, no caller persistence. Responses are never cacheable (Cache-Control: no-store). No legal effect.

## Request body

- object
  - `uid` string, required: Swiss UID in canonical or compact form. Validated locally (prefix, format, mod-11 check digit) before any lookup.

## Response `200`

Result with the same semantics as the deprecated UID-in-path operation.

## Other responses

- `400`: Malformed body, missing uid or unknown field.
- `405`: Only POST is accepted.
- `413`: Body larger than 1024 bytes (PAYLOAD_TOO_LARGE); rejected before any lookup.
- `415`: Content-Type is not application/json (UNSUPPORTED_MEDIA_TYPE); rejected before any lookup.
- `422`: Structurally invalid UID; rejected before any lookup.
- `501`: No authoritative source is configured in this deployment.

---

[API](https://skmtc.dev/bumit/apis/bumit-api.md) · [All operations](https://skmtc.dev/bumit/apis/bumit-api/llms.txt) · [OpenAPI document](https://skmtc.dev/bumit/apis/bumit-api/revisions/913e5d3654f8?raw)