/transparency/cpi_scores/search

POST /api/transparency/cpi_scores/search

Price: 10 credits

Corruption Perceptions Index scores and ranks for one edition year, 1995 to the latest, filterable by region and country name and ordered by rank.

How to use it

One row per country for the chosen CPI year, rank 1 being the least corrupt. From 2012 the score is on a 0-100 scale with sources count, standard error and confidence bounds. 1995-2011 editions use a 0-10 scale, carry rank_change against the previous edition from 1996, and from 1998 the published confidence range as score_interval, split into lower_ci and upper_ci where it is a range. score_max says which scale a row uses.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• year integer required — CPI edition year (examples: 2025, 2005; min: 1995)
• regions array nullable — Keep only countries in any of these CPI regions (one of: "AME", "AP", "ECA", "MENA", "SSA", "WE/EU")
• keyword string nullable — Text matched against the country name (examples: "guinea"; minLength: 1)
• count integer required — Max number of countries to return (min: 1)

Response

• @type string (default: "TransparencyCpiScore")
• id string required
• country string nullable
• iso3 string nullable
• region string nullable
• year integer required
• score number nullable
• score_max integer required
• rank integer nullable
• rank_change integer nullable
• sources_count integer nullable
• standard_error number nullable
• lower_ci number nullable
• upper_ci number nullable
• score_interval 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 — No CPI edition was published for that year 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.