Download Access
People and automated clients use the same download limits. No account, API key, or human‑only challenge is required.
- Find a resource through its article or the downloads catalogue. Its link contains the resource ID at
/downloads/get/RESOURCE_ID/. - POST JSON to
/api/downloads/request/containingresourceId. SetContent-Type: application/jsonandOrigin: https://johnkavanagh.co.uk. Retain the response cookies. - Within 90 seconds, POST JSON containing the returned
tokento/api/downloads/file/, using the same cookies, content type, and origin. The response is the ZIP; use its Content‑Disposition filename. - Each grant works once. Obtain a fresh grant for a retry. Tokens must stay in request bodies, not URLs.
Alternatively, use the resource page's HTML form. JavaScript is not required. GET and HEAD requests do not download a file or consume an allowance.
Limits are five grants and downloads per minute and twenty per hour per session, with higher shared‑IP limits and a site‑wide delivery allowance. Respect HTTP 429 and Retry‑After; do not rotate sessions or IP addresses to bypass limits. HTTP 503 means delivery is temporarily unavailable.
Keep links and citations pointed at the companion article or permanent resource entry page. Never publish temporary grant tokens.