/opensanctions/entities/statements

POST /api/opensanctions/entities/statements

Price: 1 credit

Get the provenance statements behind an OpenSanctions (opensanctions.org) entity's property values

How to use it

Get the raw provenance statements behind an OpenSanctions (opensanctions.org) entity — the audit trail of which source dataset asserted each property value. Each statement carries the property name (prop), the asserted value, the FtM schema, the source dataset, the source-side entity id, language, and first/last-seen timestamps. Optionally filter to a single property via 'prop' (e.g. birthDate). Returns an empty list when the entity exists but has no matching statements.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• entity string required — OpenSanctions entity id (Wikidata Q-id like 'Q7747', or internal id) or full entity URL ('https://www.opensanctions.org/entities/Q7747/'). (examples: "Q7747", "https://www.opensanctions.org/entities/Q7747/"; minLength: 1; pattern: ^(?:https?://[^\s]+|//[^\s]+|(?:www\.)?opensanctions\.org[^\s]*|[A-Za-z0-9][A-Za-z0-9._-]*)$)
• prop string nullable — Filter statements to a single property (e.g. 'birthDate', 'name', 'address'). (examples: "birthDate"; minLength: 1)
• count integer required — Max number of statements to return (min: 1)

Response

• @type string (default: "OpensanctionsStatement")
• id string required
• prop string required
• prop_type string nullable
• schema string nullable
• value string required
• original_value string nullable
• dataset string required
• source_entity_id string nullable
• lang string nullable
• first_seen string nullable
• last_seen string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Entity not found Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.