100 free credits. No credit card required.Start building
Logo
Wikipedia logoWikipedia API

Get Wikipedia articles as plain text with one API

Search Wikipedia in any language and read any article in full as plain text, with its page id, revision and disambiguation flag, as structured JSON with one SocialCrawl API key. Reads are priced in credits.

Wikipedia logo
/v1/wikipedia

2 active endpoints. Article search and full article text.

  • GET /v1/wikipedia/search
  • GET /v1/wikipedia/article

What Wikipedia endpoints does SocialCrawl ship?

Two read endpoints for every language edition of Wikipedia. Search by keyword, then read one article in full.

/v1/wikipedia/search

Articles matching search terms in one language, each with its page id, title, link, the matching passage as plain text, word count and last change. Up to 50 a page for 100 pages, with Wikipedia's total. Standard tier (1 credit).

query, language, page, limit

Article text

1 credit
/v1/wikipedia/article

One article by title or link: the whole article as plain text with its section headings, the page id, link, revision id, last change, size and whether it is a disambiguation page. Redirects are followed. A title Wikipedia does not have answers 404 and is not charged. Standard tier (1 credit).

title or url, language

Wikipedia API2 endpoints supported
View docs
Articles

Returns one Wikipedia article in any language as plain text, with its page id, link, revision and whether it is a disambiguation page.

Use it to read an article in full, for research, summaries, entity lookups or grounding an AI answer in a source.

1 credit

GET/v1/wikipedia/article?title=Python+%28programming+language%29
$ curl https://www.socialcrawl.dev/v1/wikipedia/article?title=Python+%28programming+language%29 \
    -H "x-api-key: sc_YOUR_API_KEY"
idle
// Running this live needs your own API key. Hit "Try it" to see an example response

How the Wikipedia API works

Wikipedia is a normal SocialCrawl data surface. You call GET /v1/wikipedia/… with an API key, spend credits on live misses, and get a single JSON envelope back.

Authenticate every call

Send your key in the x-api-key header. No Wikipedia account is needed for public reads. The same key works across SocialCrawl platforms.

GET with query params

Search takes query, language, page and limit. Article takes title or url, and language. Formats are validated before any charge.

Pay in credits, not seats

Every Wikipedia route costs 1 credit. Cache hits cost 0.

Read one JSON envelope

Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached. Lists also carry pagination when the route pages.

The usual integration chain

Most products search a topic once, then read the articles that matter in full.

01Search articles
GET /v1/wikipedia/search?query=…

PostList of articles with title, passage and word count

Find the right article, or the right meaning of a name.

02Read the article
GET /v1/wikipedia/article?title=…

Post with the whole article as plain text

One call gives the text, ready to split into sections.

03Read another language
GET /v1/wikipedia/article?title=…&language=de

Post for the same topic in another Wikipedia

Each language is its own Wikipedia with its own article.

request
GET /v1/wikipedia/search?query=python+programming
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here

GET /v1/wikipedia/article?title=Python+(programming+language)
response envelope
{
  "success": true,
  "data": {
    "post": {
      "id": "23862",
      "url": "https://en.wikipedia.org/wiki/Python_(programming_language)",
      "content": { "text": "Python is a high-level, general-purpose programming language. ..." },
      "ext": {
        "title": "Python (programming language)",
        "wikipedia": { "language": "en", "is_disambiguation": false, "revision_id": "1386743958" }
      }
    }
  },
  "credits_used": 1,
  "credits_remaining": 9999,
  "request_id": "req_…",
  "cached": false
}

What lands in data

Field names match the rest of SocialCrawl where archetypes align. Parse once, reuse across platforms.

PostListsearch

items[] with post.id (page id), ext.title, url, content.text (matching passage), ext.wikipedia word_count, updated_at

Postarticle

the article with content.text (plain text), ext.title, url, ext.wikipedia language, is_disambiguation, revision_id

Inside the gateway

Same request lifecycle as every other /v1 platform endpoint. Wikipedia is not a sidecar.

  1. 01

    Edge receives the call

    Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit (600/min) and concurrency (50 in flight per key).

  2. 02

    Validate, then debit

    Registry lookup finds the wikipedia route. Required params and format checks run first. Invalid input returns 400 with no charge. Valid calls debit the tier cost atomically before the read starts.

  3. 03

    Cache or fetch

    A deterministic cache key is built from platform + resource + params. Hit: return immediately, credits_used = 0. Miss: the public data is read live, with retries on 5xx or network errors and a circuit breaker if the source is unhealthy.

  4. 04

    Normalize and return

    Wikipedia data is mapped to the Post and PostList archetypes with the Wikipedia-only facts in ext.wikipedia, validated, then wrapped in the success envelope and logged for billing audit.

Billing rules that matter in production

  • search and article: 1 credit
  • Cache hit: 0 credits
  • Empty / hard fail: auto-refund
  • Bad params: 400, never charged
  • No credits: 402, never charged
  • Unknown title: 404, never charged
  • Up to 50 results a page, 100 pages
  • Article text as plain text
  • No editing or account data

How SocialCrawl gets Wikipedia data

Wikipedia data is public. We normalize it into the SocialCrawl schema so your code does not learn a second vendor SDK.

What Wikipedia is for this API

Public articles of every language edition of Wikipedia, with their page ids, revisions and links.

How SocialCrawl reaches it

Public data is read on request and normalized server-side, within each source's published usage rules.

What leaves our edge

PostList for search and Post for an article, the shared shapes. The Wikipedia-only facts sit in ext.wikipedia.

What we do not ship live

No editing, talk pages, user accounts or page history.

field map sketch
page id, title, link→ post.*page id, title, link
article text→ post.content.textarticle text, section headings
revision, disambiguation→ post.ext.wikipediarevision, last change, disambiguation

What this API is used for

The jobs this API is most often used for.

2active Wikipedia endpoints in the registry
1credit per call on every Wikipedia route

Research, entity lookups and grounding AI answers in a source

Callers search a topic or a name, then read the articles they need in full, in the languages they work in. Whole articles as plain text, in every language, in the shared Post schema, from the same key as the rest of the catalog.

Live misses read the public source on request. Repeat calls hit cache and cost 0 credits.

Use case examples

Common ways teams put this data to work, and the stack each one tends to run.

AI grounding

Python, retrieval pipelines

search a topic, then read the article to ground an answer in a cited source.

Entity research

Python, notebooks

search a company or person, check the disambiguation flag, then read the right article.

Localization

Node, scheduled jobs

read the same topic in several languages to compare how each Wikipedia covers it.

How to call the Wikipedia API

Every Wikipedia route is 1 credit. Cache hits are free.

curl "https://www.socialcrawl.dev/v1/wikipedia/search?query=python%20programming" \
  -H "x-api-key: sc_your_api_key_here"
curl "https://www.socialcrawl.dev/v1/wikipedia/article?title=Python%20(programming%20language)" \
  -H "x-api-key: sc_your_api_key_here"
Wikipedia logoWikipedia on SocialCrawl

Same key as the rest of the catalog

Endpoints

What data does the Wikipedia API return?

Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.

FAQ

Have a question? We got answers

Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.

Contact us
What does the SocialCrawl Wikipedia API cover?
It covers 2 endpoints: Article and Search. They search articles in one language and read one article in full as plain text, in the same unified JSON as the other 94 platforms.
Which languages does it support?
Every language edition of Wikipedia. Pass language as the code, for example en, de, fr or ja, or pass the article's link and the language comes from the link.
Is the article text HTML?
No. The article comes back as plain text, with section headings on their own lines, so it is ready for search, summaries or an AI pipeline.
What happens with an ambiguous title?
You get the disambiguation page, flagged in post.ext.wikipedia.is_disambiguation, and can read the meaning you want by its own title.
How much does it cost?
Each call costs 1 credit, cache hits are free, and a title Wikipedia does not have answers 404 and is not charged. You start with 100 free credits.
Is scraping Wikipedia data legal?
SocialCrawl returns publicly available Wikipedia data and does not access private or login-gated content. Whether scraping fits your project depends on your use case and jurisdiction. You are responsible for complying with Wikipedia's terms of service and applicable data-protection laws such as GDPR and CCPA. This is general information, not legal advice.
Wikipedia scraping API vs the official Wikipedia API: what's the difference?
With SocialCrawl there is no app review or approval queue. Sign up and call Wikipedia endpoints immediately with a single x-api-key. Responses share one unified schema with every other SocialCrawl platform, and credit-based pricing replaces per-platform quotas. Official APIs are still the right choice for posting and other write actions: SocialCrawl is read-only data.

Ask AI about SocialCrawl

Read the Wikipedia API reference in the docs

🤖 AI agent or LLM? Read this page as markdown