---
title: "LookupSanctionEntity"
method: GET
path: "/api/sanctions/v1/lookup-sanction-entity"
tags: ["SanctionsService"]
---

# LookupSanctionEntity

`GET /api/sanctions/v1/lookup-sanction-entity`

## Request

- Base URL: `https://api.worldmonitor.app`
- URL: `https://api.worldmonitor.app/api/sanctions/v1/lookup-sanction-entity`
- Auth: one of:
  - API key in header `X-WorldMonitor-Key`
  - API key in header `X-Api-Key`

LookupSanctionEntity screens the seeded OFAC SDN, OFAC Consolidated, Canada SEMA and US Consolidated Screening List export-control lists by name, up to 10 retained aliases per entity, or an exact IMO identifier.

## Query parameters

- `q` string
- `max_results` integer
- `jmespath` string

## Response `200`

OK

- WorldmonitorSanctionsV1LookupSanctionEntityResponse: LookupSanctionEntityResponse contains seeded matches ranked by token-set Jaro-Winkler score. A match is a lead to confirm with the issuing agency, not legal advice.
  - `results` WorldmonitorSanctionsV1SanctionEntityMatch[]
    - `id` string
    - `name` string
    - `entityType` string
    - `countryCodes` string[]
    - `programs` string[]
  - `total` integer
  - `source` string: Comma-separated lists searched; "seeded" when q is rejected before lookup; "unavailable" when no valid index records are available.

## Other responses

- `400`: Validation error
- `401`: Missing or invalid API key.
- `403`: API access requires an active subscription (the API key's subscription is inactive or expired).
- `429`: Rate limit exceeded.
- `503`: Service unavailable. Billing-verification responses include code and X-Billing-Verification; other gateway infrastructure failures use the generic GatewayError shape.
- `default`: Gateway or handler error response.

---

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