POST /api/ror/organizations
Price: 1 credit
Get a research organization from ROR by its identifier
Get full details of a research organization from the Research Organization Registry (ROR) by its identifier. Accepts the bare ROR id (02mhbdp94) or the full ROR URL. Returns the organization name, aliases, acronyms and labels, status, year established, types, domains, links, locations with geographic details, external identifiers (fundref, grid, isni, wikidata), relationships to other organizations and administrative metadata.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)organization string required — ROR identifier — the bare id (02mhbdp94) or the full ROR URL (examples: "02mhbdp94", "https://ror.org/02mhbdp94"; minLength: 1)@type string (default: "RorOrganization")id string requiredstatus string nullableestablished integer nullabletypes array (default: [])name string nullablealiases array (default: [])acronyms array (default: [])labels array (default: [])domains array (default: [])links array (default: [])@type string (default: "RorLink")type string nullablevalue string nullablelocations array (default: [])@type string (default: "RorLocation")geonames_id integer nullablename string nullablelatitude number nullablelongitude number nullablecountry_code string nullablecountry_name string nullablesubdivision_code string nullablesubdivision_name string nullablecontinent_code string nullablecontinent_name string nullableexternal_ids array (default: [])@type string (default: "RorExternalId")type string nullablepreferred string nullableall array (default: [])relationships array (default: [])@type string (default: "RorRelationship")type string nullableid string nullablelabel string nullableadmin object nullable@type string (default: "RorAdmin")created_at string nullablecreated_schema_version string nullablelast_modified_at string nullablelast_modified_schema_version string nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — Organization not found Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.