Usage notes

Code snippets

curl "https://api.oanor.com/ols-api/v1/meta" \
  -H "x-oanor-key: oanor_test_..."

await fetch("https://api.oanor.com/ols-api/v1/meta", {
  headers: { "x-oanor-key": "oanor_test_..." }
});

$ch = curl_init("https://api.oanor.com/ols-api/v1/meta");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$out = curl_exec($ch);

import requests
requests.get(
    "https://api.oanor.com/ols-api/v1/meta",
    headers={"x-oanor-key": "oanor_test_..."}
)

Example response

A real response from this endpoint, captured by the latest health check.

{
    "data": {
        "note": "OLS (EMBL-EBI Ontology Lookup Service) is a single access point to 280+ biomedical and scientific ontologies — the Gene Ontology (GO), Human Disease Ontology (DOID), Human Phenotype Ontology (HP), ChEBI (chemicals), Uberon (anatomy), EFO, Mondo, NCIT and many more. /v1/search?q=diabetes = search terms across all ontologies (or restrict with ontology=doid), returning each match's label, OBO id (e.g. DOID:9351), ontology, IRI and a short definition; /v1/term?ontology=doid&id=DOID:9351 = a single term's detail — label, definition, IRI, synonyms and obsolete flag; /v1/ontologies = browse the available ontologies with their id, title, description and term count. OBO ids look like DOID:9351, GO:0008150, HP:0000118, CHEBI:15377. Data from EMBL-EBI OLS (open). A general ontology/controlled-vocabulary lookup across many domains — broader than a single medical thesaurus (e.g. MeSH). Ideal for biomedical NLP, data annotation and harmonisation, and semantic tooling.",
        "source": "EMBL-EBI Ontology Lookup Service (OLS4) — ebi.ac.uk/ols4",
        "endpoints": [
            "/v1/search",
            "/v1/term",
            "/v1/ontologies",
            "/v1/meta"
        ]
    },
    "meta": {
        "timestamp": "2026-06-01T16:23:33.501Z",
        "request_id": "c2904bba-e4ec-4190-ad7f-4ea1b5e52675"
    },
    "status": "ok",
    "message": "Meta retrieved",
    "success": true
}