DataCite DOI Version Relationship Evidence API

Track selected version and related-identifier declarations for exact findable DataCite DOIs. Record DOI identity, title declarations, declared version, resource type, publication year, source update time and at most50 related identifier relationships and30 rights records. Useful for repository deposit QA and checking declared IsVersionOf/IsNewVersionOf/IsPartOf or other links; no relationship target is fetched or treated as verified.

At most5 DOIs, one public api.datacite.org/dois/encodedDOI request each, without enriched/affiliation/publisher expansion or credentials. JSON:API data.type/id and attributes.doi/findable state must match. A publisher may be a legacy string or a current object: only its declared name is selected. Findable state is registration metadata, not confirmation that a resource can be downloaded, reused or trusted. Missing version remains null; relation/rights truncation makes complete=false. This does not reconstruct a complete version/citation graph, detect every retraction, resolve Crossref DOIs, prove license rights, verify files, or infer chronology from a relation. Creator/contributor names, affiliations, ORCID, abstracts, subjects, content URLs and files are omitted. Selected relationship URI text is data, never followed or executed. DataCite metadata is offered under CC0; linked resources can have different rights.

Quick start

{"dois": ["10.5281/zenodo.4701802", "10.14454/qdd3-ps68"]}

Pricing and budget

0.001 USD per emitted DOI relationship observation (1 USD per1000), plus0.005 USD startup at default256MB. Higher memory can multiply startup events; check effective Store pricing. Failed/empty sources do not emit result charges; startup can still apply. At zero result budget, input validation occurs but no upstream request is sent, and rowsAvailable is null (unknown). A positive budget can request the bounded source set before output; emission stops at the result cap and complete=false/PARTIAL_BUDGET reports truncation.

Snapshot, integration and limits

Use dataset rows together with OUTPUT and SNAPSHOT. Pass SNAPSHOT.previousHashes as previousHashes in a later run. NO_BASELINE/FIRST_SEEN/UNCHANGED/CHANGED compare only selected metadata including itemKey and sourceUrl; missing records are not deletions. FIRST_SEEN means absent from the supplied baseline. There is no persistent hidden state or automatic polling. Export JSON/CSV/Excel through the default dataset.

API example: POST https://api.apify.com/v2/actors/soilair~datacite-doi-version-relationship-evidence-api/runs with your Apify Authorization header and the JSON input above. Poll the returned run; read dataset items and OUTPUT/SNAPSHOT records using its store IDs. Do not place tokens or confidential data in input. No upstream key is needed. Results live in Apify run storage according to retention; no separate analytics service.

Only fixed HTTPS provider endpoints are constructed from validated identifiers. Public-IP DNS validation, pinned connections, TLS hostname verification,2MiB decoded responses, approximately95 seconds of network budget, at most5 same-provider redirects. Official API calls are distinct from website crawling; no arbitrary URLs or HTML pages. No linked documents/files are fetched. Queries are sequential with1-second spacing. Provider403/429 or Retry-After stops later calls; retry instructions are reported and no retry/proxy/circumvention is attempted. Shared IP limits and changes to upstream services can still block runs. Caller must respect provider headers and cache/reduce repeated requests. Text is data and should not be executed.

Developed with AI assistance. Tests and live/cloud comparisons qualify the selected-field contract; they do not prove commercial demand, provider uptime or a legal/license determination. Support: share a run ID and expected fields, without credentials or private material.

References: https://support.datacite.org/docs/api-get-doi · https://support.datacite.org/docs/rest-api · https://support.datacite.org/docs/rate-limit · https://datacite.org/blog/announcing-datacites-first-public-data-file/