Zenodo

Use Zenodo data APIs through OpenAny to retrieve research-output metadata, persistent identifiers and linked materials. For record search, combine query syntax with resource, access, subject and date filters to browse up to 10,000 matches; records exceeding 100 files use files_omitted and require record details for their files. Other available operations include record citation, community search, community, research grants, record. Inspect a research output’s metadata and linked materials, retain persistent identifiers, or connect supporting files to a publication. Record metadata and file manifests identify research materials, while linked files remain separate resources with their own access conditions. Each API page provides supported parameters, request and response examples, and usage pricing.

Endpoints
9In this collection
Providers
1Unique providers
Requests
—Loading...
Success rate
—Loading...
Response P50
—Loading...
Loading statistics... API browsing remains available.

Available APIs

Zenodo community records API

Use the Zenodo community records API to retrieve research-output metadata, persistent identifiers and linked materials. Choose a community and refine its records by resource type, access, creator, subject or dates; results use the search-record shape, including explicit omission markers for oversized file listings. Inspect a research output’s metadata and linked materials, retain persistent identifiers, or connect supporting files to a publication. Record metadata and file manifests identify research materials, while linked files remain separate resources with their own access conditions. The detail page provides request and response examples, supported parameters, and usage pricing.

1 provider · 1 implementation$0.002 / billing credit

Zenodo community search API

Use the Zenodo community search API to retrieve research-community titles, identifiers and source references. Search community names or select a community type and order, then page through curated collections with descriptions and source slugs for subsequent community-details or community-record requests. Identify a curated research community, inspect its stated scope and policies, or choose a community’s record collection to browse. A community’s public description and policies identify its curation context, while its individual records require the community-record listing. The detail page provides request and response examples, supported parameters, and usage pricing.

1 provider · 1 implementation$0.002 / billing credit

Zenodo record versions API

Use the Zenodo record versions API to retrieve published versions, version identifiers and record links. Choose a Zenodo record ID, DOI or URL and browse its versions with the selected ordering; versions containing over 100 files mark omitted file and usage data explicitly. Identify a particular published version, compare version dates and identifiers, or cite the edition used in a research workflow. Version identifiers should remain attached to citations so that an older record is not silently replaced by a newer edition. The detail page provides request and response examples, supported parameters, and usage pricing.

1 provider · 1 implementation$0.002 / billing credit

Zenodo community API

Use the Zenodo community API to retrieve curated research-community metadata, policies and source references. Use a community slug, ID or URL to inspect its description, organisations, funding and public curation or visibility policies before browsing that community’s research-record collection. Identify a curated research community, inspect its stated scope and policies, or choose a community’s record collection to browse. A community’s public description and policies identify its curation context, while its individual records require the community-record listing. The detail page provides request and response examples, supported parameters, and usage pricing.

1 provider · 1 implementation$0.002 / billing credit

Zenodo record API

Use the Zenodo record API to retrieve research-output metadata, persistent identifiers and linked materials. Provide a record ID, Zenodo DOI or record URL to inspect metadata, licensing, references and the file manifest; a concept ID selects the latest version rather than every version. Inspect a research output’s metadata and linked materials, retain persistent identifiers, or connect supporting files to a publication. Record metadata and file manifests identify research materials, while linked files remain separate resources with their own access conditions. The detail page provides request and response examples, supported parameters, and usage pricing.

1 provider · 1 implementation$0.002 / billing credit

Zenodo record citation API

Use the Zenodo record citation API to retrieve formatted citations or bibliographic export data for a record. Resolve a Zenodo record ID, DOI or URL and choose a citation style, locale or export format; a concept identifier resolves to its latest version for this lookup. Prepare a citation in the required style, export bibliographic metadata, or keep references consistent across a manuscript. Citation formatting changes the representation of an existing record; it does not retrieve a paper’s full text or compare versions. The detail page provides request and response examples, supported parameters, and usage pricing.

1 provider · 1 implementation$0.002 / billing credit

Zenodo record search API

Use the Zenodo record search API to retrieve research-output metadata, persistent identifiers and linked materials. Combine query syntax with resource, access, subject and date filters to browse up to 10,000 matches; records exceeding 100 files use files_omitted and require record details for their files. Inspect a research output’s metadata and linked materials, retain persistent identifiers, or connect supporting files to a publication. Record metadata and file manifests identify research materials, while linked files remain separate resources with their own access conditions. The detail page provides request and response examples, supported parameters, and usage pricing.

1 provider · 1 implementation$0.002 / billing credit

Zenodo research grants API

Use the Zenodo research grants API to retrieve grant numbers, titles, funders, programmes and available award dates. Search grant titles, acronyms or numbers and optionally filter by a funder’s ROR ID; results describe funding awards, while associated research outputs require a separate record search. Identify an award or funding programme, compare grant metadata, or collect grant identifiers for a subsequent research-record search. Grant metadata identifies an award or programme, rather than returning all publications that acknowledge the funder or grant. The detail page provides request and response examples, supported parameters, and usage pricing.

1 provider · 1 implementation$0.002 / billing credit

Zenodo vocabularies API

Use the Zenodo vocabularies API to retrieve reference identifiers, names and supported category or filter values. Select a vocabulary such as subjects, funders, affiliations, licences or resource types, then search labels and retain the identifiers required by compatible Zenodo record-search filters. Populate a search selector, resolve the identifier expected by a related endpoint, or keep category labels consistent across requests. Returned identifiers belong to this source’s vocabulary and should be reused only in the corresponding documented filters. The detail page provides request and response examples, supported parameters, and usage pricing.

1 provider · 1 implementation$0.002 / billing credit

Common questions

How are Zenodo APIs priced?

Each endpoint publishes its own rate and billing unit. Compare the selected implementation and request-specific conditions; a collection starting price is not a quote for every request.

How do I authenticate Zenodo requests?

Use your OpenAny API key from a secure environment variable for supported account-based calls. Never paste secrets into prompts, documentation examples or public logs.

Are all implementations interchangeable?

No. Read each endpoint request schema, response examples and limitations before execution. Different suppliers may expose different fields and behavior; approve the budget before a paid call.

Use Zenodo with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.