Financial news monitoring
Use Wall Street Journal endpoints to turn financial news monitoring into repeatable API requests with documented inputs and JSON responses.
Turn a Wall Street Journal article URL into normalized JSON — title, author, publish time, word count, and body paragraphs — sourced from a public web-archive snapshot rather than the paywalled live page.
Get Wall Street Journal article content — title, author, publish time, and body paragraphs — recovered from a public web-archive snapshot, as structured JSON.
Endpoint families
2
Documented params
5
Examples
0
Live catalog snapshot
Active endpoints
2
Methods
GET
Required params
3
Schema refs
2
{
"platform": "Wall Street Journal",
"endpoint": "wsj-article",
"method": "GET",
"path": "/wsj/article",
"auth": "apiKey"
}Use cases
Get Wall Street Journal article content — title, author, publish time, and body paragraphs — recovered from a public web-archive snapshot, as structured JSON.
Use Wall Street Journal endpoints to turn financial news monitoring into repeatable API requests with documented inputs and JSON responses.
Use Wall Street Journal endpoints to turn paywalled-article research into repeatable API requests with documented inputs and JSON responses.
Use Wall Street Journal endpoints to turn content aggregation into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Wall Street Journal endpoint catalog — 2 endpoints, 5 documented request parameters, and 2 published response schemas — the same catalog Docs and Playground run against.
2 documented Wall Street Journal endpoints, grouped into 2 request families — Article and Author.
5 request parameters are documented across those Wall Street Journal endpoints, 3 of them required — the full input contract is public before you write any integration code.
2 of the 2 Wall Street Journal endpoints carry a documented response schema, so the JSON shape is known before you write any parsing code.
Wall Street Journal endpoints document their error responses (400, 403, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
2 hosted MCP tools back the Wall Street Journal endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/wsj/article
/wsj/author
Endpoint catalog
/wsj/articleReturns one Wall Street Journal article's title, byline, publication time, word count, and body paragraphs, recovered from a public web-archive snapshot of the article. WSJ serves only the first paragraphs of premium articles at the origin, so an article is returned only when a full-text archive snapshot exists; an article without one returns 404.
MCP tool wsj_article
/wsj/authorReturns one Wall Street Journal author's profile (name, job title, bio, and social links when available) and the recent articles listed on their author page, read directly from the live page. The author page sits behind the same access wall as article pages, so a nonexistent author slug returns 404.
MCP tool wsj_author
Related APIs
Media & Streaming
Research streaming catalogs, title availability, providers, offers, seasons, episodes, and release changes from JustWatch with normalized JSON.
Media & Streaming
Turn Apple Books ebook and audiobook pages into structured data — search, catalog detail, paginated customer reviews, similar titles, author bibliographies, series listings, and chart rankings as normalized JSON. Credential-free.
Media & Streaming
Search public Ticketmaster events and browse the full discovery hierarchy by category or city, with pagination plus event, attraction, and venue detail endpoints -- including fan reviews, related attractions, trending attractions, and enhanced venue branding -- for live-entertainment research.
How to scrape Wall Street Journal
The Wall Street Journal gates nearly everything, so /wsj/article looks for a public archive.today copy of a story instead of reading the paywalled page. Right now that copy is usually unreachable: in a 2026-09-25 test across six proxy pools, archive.today put every stored WSJ snapshot behind a CAPTCHA, which Crawlora does not solve. /wsj/author is unaffected because it reads the Journal's public reporter pages directly: a 2026-09-24 pull for Supreme Court reporter James Romoser returned his bio, job title, two social links, and 50 bylines from April through September 2026.
Pass a canonical wsj.com article URL to /wsj/article. Query strings and fragments are stripped and the URL canonicalized before an archive lookup runs.
The response returns title, author, published_at, word_count, and ordered body paragraphs, plus archive_url and archive_timestamp identifying the snapshot the content came from.
Pass a wsj.com/news/author/<slug> URL to /wsj/author. A successful 2026-09-24 pull for a Supreme Court reporter returned his bio, job title, two social links, and 50 bylines running from April through September 2026.
FAQ
No. /wsj/article reads a public web-archive copy rather than the live gated page, and /wsj/author reads reporter pages that wsj.com already serves publicly. Neither signs in as a subscriber, so if no archived copy of a story exists yet, there is nothing for the article endpoint to return.
Because archive.today is showing a CAPTCHA in front of its WSJ snapshots. Testing on 2026-09-25 through six different proxy pools and every request profile, the lookup found the stored snapshot each time but never got past that check. The endpoint returns a specific CAPTCHA error in that case, or a not-found error when no snapshot exists at all, and it may start returning text again if archive.today lifts the check.
It identifies which point-in-time web-archive snapshot the returned title, author, and body paragraphs were recovered from, alongside the archive_url for that specific snapshot.
A full profile read directly from the live wsj.com author page: name, job title, email, a short bio, social links, and recent articles. A 2026-09-24 pull for Supreme Court reporter James Romoser returned 50 bylined pieces spanning April through September 2026, plus his X/Twitter handle.