offshoreleaks.icij.org APIoffshoreleaks.icij.org ↗
Search entities, officers, and financial connections across Panama Papers, Pandora Papers, and more via the ICIJ Offshore Leaks API.
curl -X GET 'https://api.parse.bot/scraper/a47ab11d-1882-4b7f-9266-a0ef9239a071/search?limit=5&query=offshore' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for entities, officers, intermediaries, or addresses by keyword using the Reconciliation API. Returns matched results with relevance scores.
| Param | Type | Description |
|---|---|---|
| limit | integer | Maximum number of results to return |
| queryrequired | string | Search keyword (e.g., company name or individual name) |
| category | integer | Category filter: 0=Entity, 1=Officer, 2=Intermediary, 3=Address, 4=Other |
{
"type": "object",
"fields": {
"results": "array of search results each containing id, name, description, score, and types"
},
"sample": {
"data": {
"results": [
{
"id": "193641",
"name": "Offshore Incorporation Limited",
"score": 26.67,
"types": [
{
"id": "https://offshoreleaks.icij.org/schema/oldb/entity",
"name": "Entity"
}
],
"description": "Entity node extracted from the Offshore Leaks data."
}
]
},
"status": "success"
}
}About the offshoreleaks.icij.org API
This API provides structured access to the ICIJ Offshore Leaks Database through 5 endpoints, covering entities, officers, intermediaries, addresses, and their relationship graphs across investigations including the Panama Papers and Pandora Papers. The get_node_details endpoint returns a full connection graph — nodes with categories, properties, and statistics, plus typed edges linking related records. The search endpoint accepts keywords and an optional category filter to narrow results to specific record types.
What the API Covers
The ICIJ Offshore Leaks Database aggregates records from major investigative leak datasets — Panama Papers, Pandora Papers, and others listed in the data_sources array returned by get_database_info. The database distinguishes four record types: entities (shell companies, foundations, trusts), officers (individuals or companies with roles in those entities), intermediaries (agents or law firms that set up offshore structures), and addresses. Each record carries a numeric ID used across all endpoints.
Search and Node Details
The search endpoint accepts a query string and an optional category integer (0=Entity, 1=Officer, 2=Intermediary, 3=Address, 4=Other) along with a limit parameter. Results include an id, name, description, relevance score, and types. Pass the returned id to get_node_details to retrieve the full connection graph for that record: the response includes a data array of node objects, each with a linkurious_id, categorized properties, node statistics, and an edges array describing typed relationships to other nodes in the graph.
Bulk Listing Endpoints
list_entities and list_officers support offset-based pagination with a size parameter (max 100 per page) and an offset ceiling of 9900. Entity records expose name, country_codes, data_source, jurisdiction, status, and incorporation_date among their properties. Officer records carry name, country_codes, icij_id, data_source, and valid_until. Both endpoints return a meta object with count, from, and size, plus a links object with first, last, next, and prev URLs for navigation.
Database Metadata
The get_database_info endpoint returns no inputs and provides the database title, a description string, a license identifier, and the full data_sources array listing each investigation name and year. This is useful for validating dataset coverage before bulk querying or building source attribution into an application.
- Map the relationship graph of a named offshore entity using
get_node_detailsedges and node properties. - Bulk-export officer records with
list_officersto build a dataset of individuals named across multiple leak investigations. - Screen company names against the database using
searchwith category=0 to check for matches in offshore entity records. - Enumerate entities by jurisdiction using
list_entitiesand filtering on thejurisdictionproperty field. - Correlate
data_sourcevalues across entity and officer records to isolate records from a specific investigation like Pandora Papers. - Retrieve
icij_idfields from officer records to cross-reference individuals across ICIJ's other published datasets. - Retrieve database metadata via
get_database_infoto programmatically surface license and investigation scope in a research tool.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does the ICIJ Offshore Leaks site have an official developer API?+
What does `get_node_details` return beyond basic record fields?+
data array where each node object includes a data sub-object with categories, properties (name, country, jurisdiction, source, etc.), and statistics. Crucially, it also includes an edges array describing typed relationships to other nodes — this is what lets you traverse the connection graph between entities, officers, intermediaries, and addresses.What are the pagination limits on the list endpoints?+
list_entities and list_officers both cap size at 100 records per page and offset at 9900, meaning a maximum of 10,000 records is reachable per endpoint through standard pagination. The meta.count field shows the total number of records in the database for that type, which will typically exceed 10,000. You can fork this API on Parse and revise it to add deeper offset or cursor-based access if your use case requires it.Does the API expose intermediary records through a dedicated list endpoint?+
get_node_details, but there is no list_intermediaries bulk endpoint equivalent to list_entities or list_officers. You can fork this API on Parse and revise it to add the missing endpoint.How fresh is the data, and does the API reflect newly published investigations?+
get_database_info endpoint returns a data_sources array that lists the investigations and their years currently included. ICIJ updates the database when new investigations are released, but there is no real-time feed — coverage is tied to ICIJ's own publication schedule.