An entity with a statement summary
API · /wikidata-api
Wikidata API
The Wikidata structured knowledge graph as an API — the free, collaborative, multilingual knowledgebase that underpins Wikipedia and thousands of apps, powered by the official Wikidata action API. Search the knowledge graph by text to find entities and their Q-ids; read an entity for its label, description, aliases, a summary of its statements (each property with sample values), sitelink count and Wikipedia link; fetch the full claims for a property of an entity (values, ranks, qualifiers); resolve up to 50 Q/P ids to human-readable labels and descriptions in a single call; and look up any property's label, description and datatype. Covers tens of millions of items — people, places, organisations, works, species, events and concepts — in any language. Ideal for knowledge-graph and fact-lookup tools, entity linking and disambiguation, data enrichment, semantic search and research apps. Data is CC0.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 273 ms
- Server probes · 24h
- Subscribers
- 4,863
- active
- Total calls
- 18
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 1,000 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 1,000 calls/month
- 2 req/sec
- Search, entities & labels
- No credit card
Starter
€6.50 /month
- 35,000 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 35k calls/month
- 8 req/sec
- Claims & label resolution
- Email support
Pro
€19.50 /month
- 150,000 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- 150k calls/month
- 20 req/sec
- Entity linking & enrichment
- Priority support
Mega
€54.00 /month
- 600,000 calls / month
- 50 requests / second
- Hard cap (429 above quota, no overage)
- 600k calls/month
- 50 req/sec
- High-volume knowledge graph
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
OLS Ontology API
The EMBL-EBI Ontology Lookup Service (OLS) as an API — a single access point to more than 280 biomedical and scientific ontologies and controlled vocabularies in one place: the Gene Ontology (GO), the Human Disease Ontology (DOID), the Human Phenotype Ontology (HP), ChEBI (chemical entities), Uberon (anatomy), the Experimental Factor Ontology (EFO), Mondo, NCIt and many more. /v1/search?q=diabetes searches terms across all ontologies (or restrict to one with ontology=doid), returning each match's label, OBO id (such as DOID:9351 or GO:0008150), ontology, IRI and a short definition. /v1/term?ontology=doid&id=DOID:9351 returns a single term's detail — its label, definition, IRI, synonyms and whether it is obsolete. /v1/ontologies browses the available ontologies with their id, title, description and number of terms. OBO ids look like DOID:9351, GO:0008150, HP:0000118 or CHEBI:15377. Ideal for biomedical natural-language processing, data annotation and harmonisation, autocomplete over scientific terminology, and semantic and knowledge-graph tooling. Data from EMBL-EBI OLS (open). This is a general ontology / controlled-vocabulary lookup spanning many domains — broader than a single medical thesaurus such as MeSH.
api.oanor.com/ols-api
RxNorm API
US drug terminology as an API, powered by the U.S. National Library of Medicine's RxNav / RxNorm service. Resolve any drug or medication name to its RxNorm concept identifier (RxCUI); read a concept's properties (preferred name, term type, synonym, UMLS id); find all the related drug products for a name grouped by term type (brand names, ingredients, clinical and branded drugs, dose forms); walk related concepts by term type; list the drug classes a medicine belongs to across ATC, VA, mechanism of action, physiologic effect and chemical structure; and run spelling-tolerant search that returns candidate RxCUIs with match scores for misspelled or partial names. The standardised vocabulary that underpins US electronic health records and e-prescribing. Ideal for EHR and pharmacy systems, medication reconciliation, clinical-decision-support and health apps, and drug-data normalisation pipelines. RxCUIs are numeric.
api.oanor.com/rxnorm-api
Ontology API
Biomedical ontologies as an API, powered by the EBI Ontology Lookup Service (OLS). Search across 280+ curated ontologies — diseases (MONDO), human phenotypes (HP), the Gene Ontology (GO), anatomy (UBERON), cell types (CL), chemistry (ChEBI), experimental factors (EFO), the NCI Thesaurus and many more — to find terms by name; browse the full ontology catalogue with versions and term counts; read any term for its definition, exact synonyms, OBO id, IRI and obsolete status; and walk the class hierarchy through a term's direct parents and children. Ideal for clinical-data harmonisation and coding, biomedical search and autocomplete, knowledge-graph enrichment, annotation and curation pipelines, and research and EHR applications that need standard vocabularies. OBO ids look like MONDO:0005148 or GO:0008150.
api.oanor.com/ontology-api
Quran API
The Holy Quran as an API. Fetch any ayah (verse) by its surah:ayah reference — for example 2:255, the Ayat al-Kursi — returning both the original Arabic (Uthmani script) and a translation, along with the surah name, juz and page; read a full surah (chapter, 1 to 114) with every ayah in Arabic and translation; search the Quran for a word or phrase within a translation; and list the available translations (over 100, in English, French, Urdu, Indonesian, Turkish and many more languages). Live from the AlQuran Cloud API. Ideal for Quran reading and study apps, Islamic education and dawah tools, verse-of-the-day features and mosque or community websites. Open scripture data.
api.oanor.com/quran-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Wikidata API?
What's the rate limit for Wikidata API?
How much does Wikidata API cost?
Can I cancel my subscription anytime?
Is Wikidata API GDPR-compliant?
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/wikidata-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/wikidata-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/wikidata-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/wikidata-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.