Wikidata Scraper

Wikidata Scraper

Search Wikidata by name or phrase, or resolve a list of Q-ids into full, structured records — straight from the public MediaWiki / Wikibase API. No API key, no login.

Two modes:

• Search — free-text query (e.g. douglas adams) → matching entities with their Q-id, label and description.
• Entities — a list of Q-ids (e.g. ["Q42","Q5"]) → full records: label, description, aliases, instance-of, occupation, citizenship, a simplified claims summary, and the linked Wikipedia article.

Input

Output

One dataset row per entity.

Search mode rows:

{ ok, id, label, description, aliases[], url }

Entities mode rows:

{ ok, id, label, description, aliases[],

  instanceOf[],            // P31, as Q-ids

  occupation[],            // P106, as Q-ids

  countryOfCitizenship[],  // P27, as Q-ids

  claimsSummary,           // { Pxx: [simplified values] }

  enwikiTitle, enwikiUrl,  // linked English Wikipedia article (null if none)

  url }                    // https://www.wikidata.org/wiki/{id}

How claims are simplified

claimsSummary flattens each property's statements into a list of scalar values:

• wikibase-entityid → "Q…" (the referenced item; not re-resolved — look it up separately if you need its label)
• time → the time string (e.g. +1952-03-11T00:00:00Z)
• quantity → the amount (e.g. +1.96)
• monolingualtext / string → the text
• globecoordinate → "lat,lon"
• anything else → compact JSON, trimmed

To keep rows a sensible size, the summary keeps up to 60 properties and up to 20 values per property. instanceOf, occupation and countryOfCitizenship are surfaced as their own fields for convenience (also as Q-ids).

The multilingual (mul) fallback

Many international entities store their canonical label/aliases under Wikidata's special mul (multilingual) language rather than per-language. For example, Q42's label lives under mul, not en. This actor always requests both your chosen language and mul, so you still get label: "Douglas Adams" for Q42.

Pricing

$0.20 per 1,000 rows ($0.0002 each), plus $0.001 each time a run starts. Flat rate — no volume tiers, no plan gates — and you are charged only for rows actually returned.

You are charged one item per genuine entity row (ok: true). You are never charged for:

• empty/invalid input — a single ok: false diagnostic row with errorCode: "BAD_INPUT",
• no matches / no existing ids (NO_RESULTS),
• rate limits or network errors (RATE_LIMITED / NETWORK).

Proxy

The Wikidata API is a public, no-auth JSON API with no anti-bot, so no proxy is required and the default runs without one (saving proxy credits). Only enable Apify Proxy if you hit IP rate limits at very high volume. A descriptive User-Agent is sent on every request per Wikimedia's API etiquette.

Examples

Search:

{ "mode": "search", "query": "douglas adams", "language": "en", "maxItems": 10 }

Resolve entities:

{ "mode": "entities", "ids": ["Q42", "Q5"], "language": "en" }

Billing

Two charges apply: a $0.001 run-start fee each time a run begins, and the $0.0002 per-row fee for entity rows actually delivered. Samples, diagnostics, duplicates, blocked look-ups and no-result runs never incur the per-result fee — a run that returns nothing costs only the $0.001 start fee. Resolving a 50-id batch in entities mode therefore costs $0.011 all-in.