← AI resource directorypublic-data-apis

public-data-apis · prepared

Zenodo REST API boundary

Zenodo documentation boundaries for record reads, deposit scopes, sandbox separation and metadata harvesting; this review does not verify live API execution or reuse rights.

version 1.0.1freshness currentobserved 2026-09-06T19:38:53.679Z

resource.public-data.zenodo-rest-api
sha256:535fda10965d18722a2d34eaa6bcb1afed55257901a9f444e9e1d2d7de2ff894

Open canonical machine JSON →

Evidence-backed facts

  1. Records documentation lists GET /api/records/ and GET /api/records/:id, with size maxima of 25 for anonymous and 100 for authenticated searches. Its general all-requests-authenticated statement conflicts with this anonymous allowance; live anonymous access is unverified. informative
  2. Documented OAuth scopes separate deposit:write, which cannot publish, from deposit:actions for publication, editing and discarding edits. Tokens should remain private and travel over HTTPS in the Authorization header rather than URL parameters. informative
  3. The sandbox at https://sandbox.zenodo.org requires separate registration and tokens from https://zenodo.org, may be cleared at any time, and issues test DOIs under 10.5072 rather than production prefix 10.5281. informative
  4. For bulk access the guide recommends OAI-PMH or metadata dumps instead of search loops. OAI-PMH documents 50 records per page and two-minute resumption tokens, with expiry returning 422; metadata and file access rights must not be conflated. informative