Steps

POST an empty JSON body to /api/deposit/depositions with an Authorization: Bearer <personal-access-token> header to create a new draft deposition
From the response, take the deposition id and the bucket URL (or files endpoint) for file upload
PUT the file contents to the bucket URL (or POST to the files endpoint) to attach it to the draft deposition
PUT/PATCH deposition metadata (title, creators, description, upload_type, etc.) required for publication
POST to /api/deposit/depositions/<id>/actions/publish to finalize and mint the DOI
Read the returned DOI/doi_url from the published record; use the sandbox environment (sandbox.zenodo.org) for testing before hitting production

Known gotchas

The DOI is not registered with DataCite (and cannot be cited) until the /actions/publish step completes — draft depositions have no live DOI
Sandbox (sandbox.zenodo.org) requires a completely separate account and access token from production zenodo.org, and issues test DOIs under a different prefix (10.5072)
Publishing is irreversible for the record version — metadata mistakes on a published record require a new version, not an edit of the original files

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans

Create a Zenodo deposition, upload a file, and publish it to obtain a DOI

Steps

Known gotchas

Give your agent this knowledge — and 15,500+ more routes

Need this verified for your stack — or a route we don't have yet?