# ICIJ Offshore Leaks Database Exporter (`logiover/icij-offshore-leaks-scraper`) Actor

Export entities, officers, intermediaries, addresses and relationships from ICIJ's Offshore Leaks Database for AML/KYC, due diligence and investigative research. Filter 800K+ records without an API key.

- **URL**: https://apify.com/logiover/icij-offshore-leaks-scraper.md
- **Developed by:** [Logiover](https://apify.com/logiover) (community)
- **Categories:** News, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## ICIJ Offshore Leaks Database Exporter

Export entities, officers, intermediaries, addresses and relationships from the **ICIJ Offshore Leaks Database**. The Actor streams the official bulk archive, normalizes its collections and supports up to **500,000 records per run** without an API key.

### Who uses this data

- AML/KYC and enhanced due-diligence teams
- Corporate ownership and entity-resolution platforms
- Investigative journalists and academic researchers
- Risk, compliance and sanctions-screening analysts
- Graph/network analysis pipelines

The database contains more than 800,000 offshore entities and exposes the people, addresses, intermediaries and relationships connected to multiple ICIJ investigations.

> **Important:** A person or company appearing in the database does not imply illegal or improper conduct. ICIJ explicitly warns users to verify context and identity before reaching conclusions.

### Input

| Field | Description | Default |
|---|---|---|
| `recordType` | `entities`, `officers`, `intermediaries`, `addresses`, `others`, `relationships`, or `all` | `entities` |
| `query` | Name/address/node fragment | empty |
| `countries` | Country names or country codes | all |
| `sources` | Exact ICIJ source IDs | all |
| `jurisdictions` | Exact jurisdiction codes | all |
| `statuses` | Exact status values | all |
| `maxResults` | Maximum records, 1–500,000 | `500` |
| `includeRawRecord` | Include the complete source CSV row | `false` |

Example — Turkish entity/officer research:

```json
{
  "recordType": "entities",
  "countries": ["TR"],
  "maxResults": 25000
}
```

Example — network edges for graph analysis:

```json
{
  "recordType": "relationships",
  "maxResults": 500000
}
```

### Output

The unified output contains `recordType`, node IDs, relationship endpoints, names, status, jurisdiction, address, country values, dates, service provider, leak source and ICIJ node URL. Set `includeRawRecord` to `true` to append the complete source CSV row.

```json
{
  "recordType": "entity",
  "nodeId": "10000001",
  "name": "EXAMPLE HOLDINGS LTD.",
  "jurisdiction": "BVI",
  "countries": ["Turkey"],
  "status": "Active",
  "sourceId": "Panama Papers",
  "databaseUrl": "https://offshoreleaks.icij.org/nodes/10000001"
}
```

### API usage

```bash
curl -X POST "https://api.apify.com/v2/acts/YOUR_USERNAME~icij-offshore-leaks-scraper/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"recordType":"officers","query":"smith","maxResults":10000}'
```

### License, attribution and responsible use

The source is the [ICIJ Offshore Leaks Database](https://offshoreleaks.icij.org/pages/database). ICIJ publishes the data under its stated ODbL/CC BY-SA terms; downstream use must preserve the required ICIJ attribution and comply with those terms. Names may be shared by different people, source records may be incomplete, and historic status fields may not describe current ownership. Use the data as a research lead, not as an automated accusation or adverse-decision list.

### Changelog

- **2026-08-01 — v1.0.0:** Initial release. Added streaming export for all six collections, multi-field filtering, relationship-ready IDs, source attribution/disclaimer, optional full raw rows, 500,000-item scaling and live-source verification.

# Actor input Schema

## `recordType` (type: `string`):

Choose one node/edge collection or export all record types.

## `query` (type: `string`):

Optional case-insensitive search across names, addresses and relationship node IDs.

## `countries` (type: `array`):

Optional country names or two-letter codes, such as Turkey or TR.

## `sources` (type: `array`):

Optional source IDs, for example Panama Papers or Paradise Papers identifiers as stored by ICIJ.

## `jurisdictions` (type: `array`):

Optional exact jurisdiction codes from the source data.

## `statuses` (type: `array`):

Optional exact status values, matched case-insensitively.

## `maxResults` (type: `integer`):

Maximum matching records to save; supports bulk exports up to 500,000 items per run.

## `includeRawRecord` (type: `boolean`):

Add every source CSV field to each item. Keep off for faster high-volume graph exports.

## Actor input object example

```json
{
  "recordType": "entities",
  "query": "",
  "countries": [],
  "sources": [],
  "jurisdictions": [],
  "statuses": [],
  "maxResults": 500,
  "includeRawRecord": false
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("logiover/icij-offshore-leaks-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("logiover/icij-offshore-leaks-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call logiover/icij-offshore-leaks-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,logiover/icij-offshore-leaks-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/oZ4E9rpL2E7lIxZUJ/builds/iawtJlaFM8E9SmwiC/openapi.json