Monitor Blaze Media's news publisher
Use TheBlaze endpoints to turn monitor blaze media's news publisher into repeatable API requests with documented inputs and JSON responses.
翻译进行中。 该页面的简体中文翻译正在准备中，暂时以英文内容显示。
媒体与流媒体5 active endpointsapiKey
TheBlaze API
Blaze Media's news publisher, with verified editorial section feeds and named contributor pages. Use the content-bearing section slugs returned by discovery; sitemap paths without corresponding stories are not editorial filters. Follow canonical article URLs for the public story body and /u/<slug> for a person profile with recent stories. Keep titles and URLs for matching specific beats.
Collect Blaze Media's news publisher, with verified editorial section feeds and named contributor pages with documented TheBlaze routes.
Endpoint families
5
Documented params
9
Examples
5
Live catalog snapshot
TheBlaze coverage
Active endpoints
5
Methods
GET
Required params
7
Schema refs
5
Article1
Author1
Headlines1
News1
{
"platform": "TheBlaze",
"endpoint": "theblaze-sections",
"method": "GET",
"path": "/theblaze/sections",
"auth": "apiKey"
}Use cases
Workflows that fit TheBlaze
Collect Blaze Media's news publisher, with verified editorial section feeds and named contributor pages with documented TheBlaze routes.
Separate TheBlaze feed records from article or profile follow-up
Use TheBlaze endpoints to turn separate theblaze feed records from article or profile follow-up into repeatable API requests with documented inputs and JSON responses.
Preserve source URLs, dates, and access outcomes for review
Use TheBlaze endpoints to turn preserve source urls, dates, and access outcomes for review into repeatable API requests with documented inputs and JSON responses.
Managed execution
How Crawlora handles this platform
Every figure below is read from the live TheBlaze endpoint catalog — 5 endpoints, 9 documented request parameters, and 5 published response schemas — the same catalog Docs and Playground run against.
Documented endpoint coverage
5 documented TheBlaze endpoints, grouped into 5 request families — Article, Author and Headlines, plus 2 more.
Published request surface
9 request parameters are documented across those TheBlaze endpoints, 7 of them required — the full input contract is public before you write any integration code.
Known response shape
5 of the 5 TheBlaze endpoints ship a recorded example response, and 5 carry a documented response schema — you can code against the real JSON before the first request.
Documented failure modes
TheBlaze endpoints document their error responses (400, 404 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.
Agent-callable MCP tools
5 hosted MCP tools back the TheBlaze endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
Know what the API can collect before integrating
1 endpoints
Article
/theblaze/article
GETapiKey
1 endpoints
Author
/theblaze/author
GETapiKey
1 endpoints
Headlines
/theblaze/headlines
GETapiKey
1 endpoints
News
/theblaze/news
GETapiKey
1 endpoints
Sections
/theblaze/sections
GETapiKey
Endpoint catalog
TheBlaze API endpoints
GETapiKeyexample
/theblaze/articleGet a Blaze Media article
Returns one TheBlaze (Blaze Media) article by `url`, a canonical HTTPS editorial or show-story link on `theblaze.com`; non-editorial paths and off-site URLs are rejected. The response has the title, description, section, authors, publication and update times, image URL, body `paragraphs` and a `paywalled` flag.
MCP tool theblaze_article
url:queryx-api-key:header
GETapiKeyexample
/theblaze/authorGet a Blaze Media contributor profile
Returns a public /u/<slug> profile and up to 30 recent article feed items. Provide exactly one of slug or canonical profile URL.
MCP tool theblaze_author
slug:queryurl:queryx-api-key:header
GETapiKeyexample
/theblaze/headlinesGet Blaze Media section headlines
Returns up to 30 recent stories from one TheBlaze (Blaze Media) section. `section` is required, case-sensitive and must match exactly, for example `news`, `columns/opinion`, `lifestyle/men`, `tech` or a show such as `shows/relatable`. Other values are rejected. Items have a title and URL, plus summary, author, publication time and image when the outlet provides them.
MCP tool theblaze_headlines
section:queryx-api-key:header
GETapiKeyexample
/theblaze/newsGet Blaze Media top stories
Returns the latest site-wide stories from TheBlaze (Blaze Media), up to 30 items, covering news and opinion. Each item has a headline, canonical URL, publication time, byline, summary and image URL when published. It takes no parameters.
MCP tool theblaze_news
x-api-key:header
GETapiKeyexample
/theblaze/sectionsList Blaze Media sections
Returns all verified article-bearing editorial and show sections accepted by the headlines endpoint. The contributors collection is included; the off-site Profile feed is excluded.
MCP tool theblaze_sections
x-api-key:header
Related APIs
More 媒体与流媒体 coverage
Media & Streaming
FUSSBALL.DE
Follow German football from the Bundesliga down to the lowest Kreisklasse. Discover competitions in all 22 federations, then read matchdays, standings, scorers, clubs, teams, and players from the DFB's own amateur-football portal.
Media & Streaming
Sportskeeda
Browse Sportskeeda's sports and entertainment coverage, community wikis, quizzes, and fan games with the catalog's current slugs and filter limits.
Media & Streaming
JustWatch
Research streaming catalogs, title availability, providers, offers, seasons, episodes, and release changes from JustWatch with normalized JSON.
How to scrape TheBlaze
Extract TheBlaze data in 5 steps
TheBlaze is Blaze Media's news publisher, with verified editorial section feeds and named contributor pages. A live /theblaze/sections response on 2026-10-14 contained 44 section records; refresh it before scheduling because publisher feeds change. Use the content-bearing section slugs returned by discovery; sitemap paths without corresponding stories are not editorial filters. Follow canonical article URLs for the public story body and /u/<slug> for a person profile with recent stories. Keep titles and URLs for matching specific beats. Search is intentionally absent because observed later pages repeated the same results and empty states were ambiguous. Article and profile routes were verified, but a sitemap alone does not guarantee pagination. Use the endpoint cards for this integration's accepted inputs. Publisher reference: https://www.theblaze.com/
- Step 1
Refresh TheBlaze's editorial inventory
A live /theblaze/sections response on 2026-10-14 contained 44 section records; refresh it before scheduling because publisher feeds change. Use the content-bearing section slugs returned by discovery; sitemap paths without corresponding stories are not editorial filters. Follow canonical article URLs for the public story body and /u/<slug> for a person profile with recent stories. Keep titles and URLs for matching specific beats.
- Step 2
Plan around TheBlaze's source-specific constraints
Use a discovered content-bearing section slug; sitemap-only paths are not proven filters. Article URLs and /u/<slug> contributor profiles are supported, but search and reliable pagination were not established, so keep each call scoped to a verified section or profile.
- Step 3
Carry TheBlaze section context into each headline pull
Use a discovered content-bearing section slug; sitemap-only paths are not proven filters. Article URLs and /u/<slug> contributor profiles are supported, but search and reliable pagination were not established, so keep each call scoped to a verified section or profile. Pass only a value returned by /theblaze/sections and accepted by /theblaze/headlines; preserve the selected desk with its results.
- Step 4
Check TheBlaze article access before using body text
Search is intentionally absent because observed later pages repeated the same results and empty states were ambiguous. Article and profile routes were verified, but a sitemap alone does not guarantee pagination. Keep teaser, truncation, premium, or access fields beside the canonical URL so downstream users can see what the publisher actually returned.
- Step 5
Use TheBlaze's contributor route for its documented purpose
Use the content-bearing section slugs returned by discovery; sitemap paths without corresponding stories are not editorial filters. Follow canonical article URLs for the public story body and /u/<slug> for a person profile with recent stories. Keep titles and URLs for matching specific beats. Search is intentionally absent because observed later pages repeated the same results and empty states were ambiguous. Article and profile routes were verified, but a sitemap alone does not guarantee pagination.
FAQ
Scraping TheBlaze: common questions
How should I scope a TheBlaze headline pull?
A live /theblaze/sections response on 2026-10-14 contained 44 section records; refresh it before scheduling because publisher feeds change. Use the content-bearing section slugs returned by discovery; sitemap paths without corresponding stories are not editorial filters. Follow canonical article URLs for the public story body and /u/<slug> for a person profile with recent stories. Keep titles and URLs for matching specific beats.
What should I preserve when using TheBlaze's article route?
Search is intentionally absent because observed later pages repeated the same results and empty states were ambiguous. Article and profile routes were verified, but a sitemap alone does not guarantee pagination.
Can TheBlaze sitemap paths be used as sections?
Only content-bearing slugs returned by section discovery were validated. A sitemap can include paths that do not represent a working editorial feed, and search results repeated or returned ambiguous empty states, so do not build a crawler that infers section support from URL presence alone. For a known contributor, use the /u/<slug> profile form and keep the resulting recent-story cards separate from section headlines.