Zenodo Record Concept Version & License Watch API
Pricing
from $1.00 / 1,000 metadata observations
Zenodo Record Concept Version & License Watch API
Resolve public Zenodo record/concept IDs and watch version, DOI, access and license declarations. Explicit resolution type and change snapshots; no files, author profiles or rights clearance.
Pricing
from $1.00 / 1,000 metadata observations
Rating
0.0
(0)
Developer
Salih Can Kurnaz
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Read at most five known public Zenodo record/concept IDs. A concept ID may redirect to the current record. Verify that the returned ID equals the requested record or that conceptrecid equals the requested concept; emit requestedId, recordId and explicit EXACT_RECORD or CONCEPT_TO_CURRENT_RECORD resolution. This avoids silently representing a concept ID as an immutable version. Keep DOI/concept DOI, concept ID, title, declared version, access right, resource type, license ID and modified timestamp. No search, file downloads, file manifest, descriptions, authors, owners, affiliations, views/download statistics or restricted content. License/access fields are declarations and may be absent; this is not legal permission, ownership verification, plagiarism detection or proof of unrestricted file access. Same-host redirects are allowed but cross-host requests are refused. A Retry-After header stops further provider requests even when metadata was returned successfully. No missing record is called deleted or withdrawn without explicit source evidence.
Input example
{"recordIds": [3555620],"maxResults": 2}
Results, snapshots and coverage
Each saved observation is a dataset row with itemKey, contentHash, observedAt and sourceUrl. The hash covers selected semantic fields and excludes volatile retrieval times and request URLs. Copy SNAPSHOT.previousHashes into the next input to compare the same watchlist: NO_BASELINE, FIRST_SEEN, UNCHANGED or CHANGED. There is no automatic durable cross-run memory; only the baseline you provide is compared. Unchanged successful rows are still billed. Missing rows never prove deletions. OUTPUT reports rowsEmitted, actual requestCount, source coverage, errors and completion status. The snapshot complete flag is false when any source fails, a provider stops further requests, or the result/budget cap prevents completion.
Pricing and budget protection
Pay per event: $0.005 startup plus $0.001 per saved observation. Startup quantity follows Apify memory rules (minimum one). Default memory256 MB and timeout120 seconds. No browser, proxy, paid external API, credentials or account-wide permissions. The runtime checks the effective result budget before contacting sources and before saving rows; zero affordable rows causes no source work. Provider list limits are reduced to the remaining affordable capacity. The run has a90-second fetch deadline, two-MiB decoded-body limit, no network retries and no pagination. API rate403/429 or Retry-After stops additional sources. All-source failure exits with an error and a preserved OUTPUT; partial successful observations remain available. Public data or its upstream API may be free: the event fee pays for this bounded workflow, data selection, output validation, snapshots and Apify execution. It does not buy exclusive data or imply endorsement by the provider.
Access and limitations
Only constructed official HTTPS API endpoints are contacted. Arbitrary URLs, private addresses, cross-provider redirects and credential-bearing input are rejected. Provider rate limits and shared-IP quotas apply across runs; do not use parallel runs to defeat a provider limit. For large/bulk extraction use the provider's supported bulk service. This is selected metadata, not independent validation of every source declaration. No guarantee of source availability, completeness, commercial return or suitability for high-stakes decisions is made.