UN Consolidated Sanctions API Guide with Apify

Stream official UN XML through a maintained Apify Actor with filters, schedules, and dataset exports. The UN Sanctions List Scraper turns each public UN consolidated-list record into a bounded Apify dataset row and preserves a direct source URL for verification.

Start with a reviewable sample

{"recordType":"Entity","queries":[],"regimes":[],"maxResults":500}

Begin with ten to one hundred records, not a full archive. Inspect identifier stability, date formats, nulls, arrays, free-text fields, and source links. Start with entities or one regime, validate output, then expand within a documented review process. Once the sample matches the intended workflow, raise the result limit deliberately and save the input as a named Apify Task.

Design the dataset around source truth

Keep data ID, permanent reference number, record type, primary and original-script names, aliases, regime, listing date, update dates, nationalities, addresses, comments, and source URL together in the raw landing table. Do not replace missing values with zero, invent status labels, or silently collapse aliases. Use the publisher's stable identifier as the upsert key where one exists; otherwise combine the canonical source URL and observed identifier. Add a downstream collection timestamp so analysts can distinguish a revised record from a newly published record.

A useful pipeline has three layers. The raw layer stores the Actor output without lossy transformations. The review layer adds normalized dates, currencies, or matching candidates while preserving original fields. The application layer contains only decisions that have passed the organization's validation rules. This separation makes source changes auditable and prevents a convenient spreadsheet formula from becoming an undocumented business rule.

Schedule changes without creating alert noise

Run the Task on a cadence appropriate to how often United Nations Security Council changes. Compare stable keys and material fields rather than array order or page position. Send alerts only for additions, removals, deadline changes, status changes, or other changes relevant to the workflow. Store the previous snapshot in a table or object store and make the diff reproducible.

For operational use, log the Actor run ID, dataset ID, input, source URL, and collection time. Use retries for transient network failures, but fail visibly when the publisher returns no records for a query that normally has coverage. Silent empty datasets are more dangerous than explicit failures because they can look like a legitimate all-clear.

Validate before acting

The consolidated list spans distinct Security Council regimes with different measures and criteria. A name match is not identity resolution. Verify the permanent reference, identifiers, committee context, and current official record with human review. The Actor is a collection tool, not a substitute for due diligence, legal interpretation, financial analysis, or publisher methodology. Reviewers should open the source URL, confirm that the record is current, and document the evidence used for any material conclusion.

This workflow is designed for sanctions researchers, compliance teams, policy analysts, and auditors. It is an independent integration and is not affiliated with or endorsed by United Nations Security Council.

Endpoint and schema details

The stable entry URL is https://scsanctions.un.org/resources/xml/en/consolidated.xml. It responds with a redirect to a signed Microsoft Blob URL, so clients must follow redirects without persisting the temporary destination. The root contains INDIVIDUALS and ENTITIES; each child has identifiers, names, list type, dates, and nested identity context.

Streaming matters even though the file is only a few megabytes today. It bounds memory, starts producing filtered matches before the entire tree is materialized, and scales if the list grows. The Actor retries transient network errors, stops at the explicit result cap, and raises when a filtered search produces no records.

Use entity or individual mode for focused applications and full mode for controlled archives. Apify's dataset API provides run-scoped output; Tasks make the exact filters repeatable. Always retain the official page URL because transport success does not answer how a committee's measures apply.

Why use an Apify Task

A Task makes the exact input repeatable across schedules, webhooks, the API, Make, Zapier, n8n, and MCP clients. Keep one Task per business question instead of one enormous catch-all export. Small Tasks are easier to test, cheaper to rerun, and clearer when a source field or filter changes. The Thirdwatch Actor on Apify provides JSON, CSV, Excel, RSS, and API access to the resulting dataset.