ROR Organization Record Change Evidence API

Check selected Research Organization Registry v2 record state for exact known ROR IDs. Return declared status, all display-name values, name/type/language tuples, organization types, domains, links and parent/child/related/predecessor/successor declarations, plus declared establishment and schema/update dates. Useful for institution-ID metadata QA and affiliation registry maintenance.

At most5 bare IDs, one fixed api.ror.org/v2/organizations/ID request each. Returned full id must equal the requested ROR URL. Public inactive/withdrawn records can be retrieved by exact ID and are preserved rather than hidden. Not a business register or legal/entity verification, recommendation, accreditation or affiliation match. No person/contact profile, name search, fuzzy matching, corporate ownership inference or fetching linked websites. ROR displays one or more names; no universal primary name is invented. Lists are bounded and excessive names/relationships/links/domains fail as source errors rather than silently losing evidence. External IDs and geographic fields are omitted from this selected contract. Source status/relationships are declarations and can be revised. Dataset metadata update dates participate in the hash. Use the official ROR data dump for whole-registry access; this Actor does not enumerate it.

Quick start

{"rorIds": ["03yrm5c26", "00tjv0s33"]}

Pricing and budget

0.0007 USD per emitted organization record observation (0.7 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~ror-organization-record-change-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://ror.readme.io/docs/rest-api · https://ror.readme.io/docs/api-single · https://ror.readme.io/docs/ror-data-structure