UK 360Giving Dataset Publication Watch

UK grantmakers publishing and republishing their grants data to the 360Giving Standard: who published, what changed, the licence, and a direct link to the file. Withdrawals are reported too - a dataset leaving the registry is a take-down signal you need, not a row to drop quietly.

Source and the routes that are CLOSED

https://registry.threesixtygiving.org/data.json - public, logged-out, no key, HTTP 200, 745,926 bytes. 360Giving's own take-down policy names this feed: "These links are curated by 360Giving on the 360Giving Data Quality Dashboard and as a JSON feed."

Probed 2026-07-29 and not used, with the reason:

route	why not
GrantNav /search, /recipients, /funders	robots.txt Disallow for User-agent: *
analytics.threesixtygiving.org	robots.txt Disallow: /
store.data.threesixtygiving.org	HTTP 401 on every path, including its robots.txt

Measured on the registry: 873 datasets, 292 publishers, every entry carrying a modified timestamp. Licences: CC BY 4.0 696, OGL 3.0 121, CC BY-SA 4.0 35, CC0 21.

Rate: 2 requests per second, strictly

360Giving asks for no more than two requests a second. Every call this Actor makes goes through a token bucket whose capacity is pinned to one token, so the first request goes immediately and every one after it waits the full interval. A bucket that starts full is not a limiter - it passes its whole capacity instantly, which is how an earlier cell in this fleet sent 13.3 req/s against an 8/s cap.

Take-down and retention - YOUR duty, not just ours

360Giving's take-down policy is explicit that once data is open it "may be taken and used by different people in different applications that are beyond 360Giving's control", and that when a take-down happens they "will notify the owners of any of the online applications ... and advise them on any actions they may need to take".

If you cache what this Actor emits, you are one of those applications. So:

• a dataset or grant that disappears from the source is emitted as a REMOVED delta with is_withdrawal: true - never dropped quietly, because you are the one who has to act;
• every record carries take_down_policy linking 360Giving's policy;
• every record carries license_name; most of this data is CC BY 4.0 and attribution is a licence condition, not a courtesy;
• grant records name identifiable individuals and organisations. Deleting on withdrawal is a data-protection obligation you inherit with the copy.

Read the policy: https://www.threesixtygiving.org/take-down-policy/

Pricing

Pay-per-event on the ratified four-tier ladder (FREE → GOLD, with Platinum and Diamond floored at the Gold rate). Apify applies its own plan discount on top.

Event	FREE	BRONZE	SILVER	GOLD
Actor start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Source check (source-check)	$0.10	$0.09	$0.08	$0.067
Dataset-publication delta (g360-delta)	$0.10	$0.09	$0.08	$0.067

source-check is charged once per run, after the source enumeration terminates — seed runs and no-change runs included. It is not charged when the source refused the read, an unnamed funder, an unsupported format or an oversized file.

g360-delta is charged per emitted delta, in watch mode only. Seed runs and no-change runs charge nothing here.

apify-actor-start is the platform's reserved event, never charged in this code. The Actor is clamped to 1024 MB on both settings, so it is charged exactly once per run — the platform bills it once per gigabyte of run memory.

Snapshot mode is a PREVIEW

watch_mode: false returns at most 25 records, hard-capped in code and labelled output_mode: "preview". This Actor sells change detection, not bulk export.

Watch semantics

The first watch run stores a private baseline and emits zero deltas. Billed deltas are capped at 500 per run; the overflow is a named PARTIAL withholding, never billed, and re-detected next run.

One slice per Actor

This Actor emits dataset-publication and nothing else. Its sibling reads 360Giving for the other slice, each with its own baseline and its own price.

Terminal states

NORMAL - SUCCEEDED-0: GENUINE_EMPTY - SUCCEEDED-0 (no change) - PARTIAL - BLOCKED. A zero with no evidence FAILS loud. A funder name that matches nothing FAILS naming the registry, and a file that arrives and does not parse FAILS naming what arrived - neither is ever reported as an empty source.