How to Scrape Wikidata Entities
Search or fetch Wikidata entities with labels, descriptions, aliases, claims, and sitelinks.

Wikidata pages connect entities to a large structured graph, but a normal application often needs a bounded set of readable fields rather than an open-ended query. The Wikidata Entity Scraper combines name search and exact Q-ID retrieval into Apify dataset rows.
Choose search or exact lookup
Search is useful for discovery; exact IDs are safer for repeat enrichment.
{"queries":["Ada Lovelace"],"entityIds":["Q42"],"language":"en","maxResultsPerQuery":5}Results include label, description, aliases, search-match context, simplified claims, statement and sitelink counts, and direct Wikidata and Wikipedia URLs. Review search matches before treating an ID as resolved. A shared name can identify a person, work, organization, or technology.
For exact-only work, set queries to an empty list. The Actor does not inject a default search when IDs are supplied. Store the Q-ID as the durable key and treat labels as mutable display data. Language affects search and readable metadata, not the entity's identity.
Claims are keyed by Wikidata property IDs. Values are simplified for portability; qualifiers, references, ranks, units, and precision are not expanded into a complete RDF representation. Use the entity page or a specialized graph workflow when those details matter.
After validation, save a Task and schedule refreshes. Community-maintained values can change, so retain collection dates and source links. The output supports enrichment and discovery while preserving the boundary between a convenient flattened record and the full knowledge graph.
Frequently asked questions
Can I fetch exact Q-IDs without search?
Yes. Provide entityIds and leave queries empty.
What license applies to structured Wikidata data?
Wikidata publishes its structured data under CC0 1.0.
Related
100 free credits, no credit card.
About 30 real searches. Add the MCP to Claude or Cursor in two minutes.