Social Fetch
Start for freeStart free
All platforms26 Wikipedia endpoints

Wikipedia API. Pages, history and Wikidata as JSON.

Page records, article bodies, edit history, links, categories, pageviews and Wikidata in one API. Pick an edition, name a title, get JSON.

Get 100 free credits
No credit card requiredRead the API docs
  • Any Wikipedia edition
  • Wikipedia + Wikidata
  • 1 credit per request
  • Failed requests aren't charged
99.8% uptime#3 Product of the Day3,200+ developers

Teams running monitoring, research, and enrichment pipelines

Why Social Fetch

Wikipedia data as JSON. You build the product.

Live Wikipedia data in one response shape, with platform changes handled for you.

Wikipedia, plus every other platform

One key and one response envelope for Wikipedia and 56 more platforms.

Pricing you can reason about

One request, one credit. Know how far your balance will go before you run your next batch.

Live data on every request

Fetch public data when you ask for it.

Nothing to maintain

We handle platform changes and breakages.

Built for production jobs

Run concurrent workloads with explicit statuses and request IDs.

Regular jobs. Better rates.

Running lookups every month? Get lower per-credit rates with a monthly plan. For occasional projects, choose pay as you go.

Never expires

What Wikipedia data can you get?

26 endpoints, one API key. Every response comes back as live JSON in the same envelope.

Browse all 26 Wikipedia endpoints

Pages

History

Links

Media

Pageviews

Search

Categories

Geo

Feeds

Changes

Users

Wikidata

Random

Use cases

What teams build with Wikipedia data

Monitoring, enrichment, research and content workflows on Wikipedia data, on the same API as every other platform.

What you can build

Watch pages and attention

Follow recent changes, revisions and pageviews.

Add reference data

Pull article text, Wikidata entities and SPARQL results into your records.

Browse all workflows →

How it works

Your first request in three steps.

Use TypeScript or your automation tool of choice.

Sources

+ 51 more platforms

One request

Social Fetch API

GET/v1/tiktok/profiles/charlidamelio

x-api-key: sk_live_••••••••

1 request · 1 credit

Same JSON shape

response.json200 OK
{
  "data": {
    "lookupStatus": "found",
    "profile": {
      "platform": "tiktok",
      "handle": "charlidamelio",
      "displayName": "charli d’amelio",
      "verified": true
    },
    "metrics": {
      "followers": 160263648
    }
  }
}

  1. Step 1

    Create your free account

    Get an API key with 100 requests included.

  2. Step 2

    Choose an endpoint

    Pass a username, URL, keyword, or post ID.

  3. Step 3

    Get clean JSON

    Use the response immediately or send it into your pipeline.

Works with your stack

Code, automate, or connect your AI.

Explore integrations

Pricing

Social data, priced simply.

Start with 100 free credits. Monthly plans give you predictable volume and lower per-request rates.

Starter

$29.00

18,000credits

$1.61 per 1k · $0.00161 per request

  • Top up from $1.61 / 1k if you run out
  • Up to 25 monitors
Subscribe to Starter
Most popular

Growth

$79.00

50,000credits

$1.58 per 1k · $0.00158 per request

  • Top up from $1.58 / 1k if you run out
  • 5 team seats
  • Up to 100 monitors
Subscribe to Growth

Scale

$225.00

150,000credits

$1.50 per 1k · $0.00150 per request

  • Top up from $1.50 / 1k if you run out
  • 25 team seats
  • Up to 250 monitors
Subscribe to Scale
  • Cancel anytime
  • 30-day money-back guarantee
  • Price locked while you stay

Need 1M+ credits, invoicing, or volume rates? Talk to us

Trust signals

DevHunt

Product Hunt

Uneed

Customers

Teams building on Social Fetch.

“Our TikTok and Instagram scrapers broke constantly. Social Fetch took us off that rotation — we ship product again.”

Daniel Reeve · Founder, Social Crow

  • “Transcripts at volume from one endpoint. No broken scrapers for our small team to maintain.”

    Marcus Lin · Founder, Voice Gecko

  • “Live profile data on every request. We never flag accounts from a stale cache.”

    Hannah Webb · Founder, Scam Finder

  • “Heavy concurrent load, no rate limits to negotiate. The rare API I haven't wrapped in retries.”

    Owen Pritchard · Founder, IP Flare

Wikipedia API: common questions

Which Wikipedia editions can I read?

Any edition with a code such as en, de, ja, zh or zh-hant. Pass it as lang. The default is en. Titles are read on the edition you choose, so a title that exists on one edition can be not_found on another.

How do I name a page title?

Use the title as it appears in the page URL, for example Albert Einstein, C++ or Category:Living people. Spaces and underscores both work, and a #fragment is dropped. Titles are limited to 255 bytes and may not contain a pipe, control characters, or the characters < > [ ] { }.

What is the difference between the page and content routes?

GET /v1/wikipedia/pages/{title} returns the page record: identity, namespace, Wikidata id, description, lead extract, images, coordinates, protection, category counts and optional search-index data. GET /v1/wikipedia/pages/{title}/content returns the article body as plain text, HTML or wikitext, with sections, categories, templates and links.

Does HTTP 200 mean the page exists?

No. HTTP 200 means the request finished. Check data.lookupStatus. found means the page or entity was returned; not_found means it does not exist on that edition. A found list with no rows also sets data.empty to true.

Can I fetch several pages at once?

Yes. GET /v1/wikipedia/pages takes up to 20 titles separated by a pipe, for example titles=Albert Einstein|Barack Obama. Each entry in data.pages keeps its requestedTitle and its own lookupStatus, so a mix of found and missing titles is one successful call.

How far back can I read pageviews and history?

Pageview routes take from and to as ISO 8601 dates or times, with daily or monthly granularity, and return one row per day or month in that range. History and list routes return at most 500 rows per page and continue through data.page.nextCursor. Data starts at the dates it publishes; a range with no rows is found with empty set to true.

What can I do with Wikidata?

GET /v1/wikipedia/wikidata/entities/{id} returns an item, property, lexeme or media entity by id such as Q937 or P31. Add site=enwiki and pass a page title instead of an id to resolve that page's entity. GET /v1/wikipedia/wikidata/search finds entities by label, alias or description, and GET /v1/wikipedia/wikidata/query runs a read-only SPARQL query and returns the variable names, bindings and row count.

How much does the Wikipedia API cost?

Most routes charge 1 credit per completed request. The batch route charges 1 credit per requested title, up to 20 per call. Each page of a list is billed separately. Check meta.creditsCharged on every response. New accounts start with 100 free credits.

Can I use these routes from agents or MCP?

Yes. Every Wikipedia route is a typed MCP tool and can also be reached through Ask (POST /v1/ask) in plain English. Use the typed routes for production jobs and the MCP tools when an assistant needs to look something up.

The Wikipedia API in detailHow the Wikipedia routes work, what they cost, and how they differ from the official API.

Why teams use Social Fetch for Wikipedia

Social Fetch exposes 26 routes under /v1/wikipedia. Most routes take lang, an edition code such as en, de, ja or zh-hant, so the same call works across Wikipedia editions. Every route that covers an edition, including Wikidata search, takes lang, and the SPARQL route needs no edition. Page routes also take a title exactly as it appears on the edition, including prefixes such as Category:Living people or Talk:Barack Obama.

Pages and history come from the page, batch, content, revisions and history-stats routes. The links and structure routes cover backlinks, internal and external links, language editions, media and category members. Discovery covers full-text search, prefix suggestions, nearby pages and random pages. Traffic and recency cover per-article pageviews, the most-viewed list, site totals, the featured feed, on-this-day entries, recent changes and public logs. People come from the user and contributions routes. Wikidata comes from the entity, search and read-only SPARQL routes.

Every response is the { data, meta } envelope. data.lookupStatus is found or not_found, so a missing page, user or entity is a typed answer instead of an error. Lists page with an opaque cursor from page.nextCursor; when page.hasMore is false the walk is over. Nearby pages is the exception: it returns the nearest limit results and has no cursor. Counts and version fields are Wikipedia's own, never invented.

How to call the Wikipedia API

  1. 1. Create an API key

    Sign up at Social Fetch and copy a key (sfk_...). New accounts get 100 free credits, enough to try each route on a few pages.

  2. 2. Choose the edition and route

    Send x-api-key on every request. Use lang=en for English, or lang=de for German. For example GET /v1/wikipedia/pages/Albert%20Einstein returns the page record and GET /v1/wikipedia/search?query=einstein&lang=en returns search hits.

  3. 3. Branch and page

    Check data.lookupStatus before storing a row. Follow data.page.nextCursor while data.page.hasMore is true. Bill from meta.creditsCharged.

What each Wikipedia route returns

  • Page records with title, namespace, Wikidata id, description, lead extract, images, coordinates, protection and revision data.
  • Article content as plain text, rendered HTML or wikitext, with sections, categories, templates, images and external links.
  • Full revision history, edit and editor counts, backlinks, internal and external links, language editions and media.
  • Full-text search with match ranges and total hits, plus prefix suggestions, category members, nearby pages and random pages.
  • Daily or monthly per-article views, most-viewed articles and countries, and site-wide views or unique devices.
  • The featured feed, on-this-day entries, recent changes and public logs, filtered by type, page, namespace or time.
  • Public user records and contribution lists, with block, group and registration data.
  • Wikidata entities by id or wiki title, entity search, and read-only SPARQL query results.

How much does the Wikipedia API cost?

Most Wikipedia routes charge 1 credit per completed request. The batch route charges 1 credit per requested title, up to 20 titles per call. Each page of a list is its own request. Credits never expire on pay-as-you-go packs, and meta.creditsCharged on every response is the billing source of truth.

Social Fetch vs the official Wikipedia API

Wikipedia and Wikidata publish their own JSON APIs, but each surface has a different shape: page records, rendered content, revision lists, pageview metrics and SPARQL results all look different. Social Fetch gives every route the same { data, meta } envelope, the same lookupStatus, the same cursor block and the same edition parameter, so one client can read a page, its history and its views without a separate adapter for each.

Pull your first Wikipedia data.

Run a live Wikipedia request in the playground. 100 free credits, no card, JSON back in seconds.

Get 100 free credits

No credit cardSign up in 30 seconds withGoogleGitHub