Monitor Blaze Media's news publisher
TheBlazeエンドポイントを使えば、「Monitor Blaze Media's news publisher」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
翻訳作業中です。 日本語訳を準備中のため、このページは一時的に英語で表示されます。
メディア・ストリーミング稼働中エンドポイント 5件apiKey
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.
エンドポイントファミリー
5
ドキュメント化されたパラメータ
9
サンプル数
5
ライブカタログスナップショット
TheBlazeのカバレッジ
稼働エンドポイント
5
メソッド
GET
必須パラメータ
7
スキーマ参照
5
Article1
Author1
Headlines1
News1
{
"platform": "TheBlaze",
"endpoint": "theblaze-sections",
"method": "GET",
"path": "/theblaze/sections",
"auth": "apiKey"
}ユースケース
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
TheBlazeエンドポイントを使えば、「Separate TheBlaze feed records from article or profile follow-up」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Preserve source URLs, dates, and access outcomes for review
TheBlazeエンドポイントを使えば、「Preserve source URLs, dates, and access outcomes for review」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
Crawloraによるこのプラットフォームの処理方法
以下の数値はすべて、稼働中のTheBlazeエンドポイントカタログから取得しています（エンドポイント5件、ドキュメント化されたリクエストパラメータ9個、公開レスポンススキーマ5件）。DocsとPlaygroundが参照しているカタログと同じものです。
ドキュメント化されたエンドポイント
TheBlazeのエンドポイントは5件、5つのリクエストファミリーに分類されています（Article、Author、Headlinesほか2件）。
公開されたリクエスト仕様
これらのTheBlazeエンドポイントには9個のリクエストパラメータがドキュメント化されており、うち7個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
判明しているレスポンス構造
5件のTheBlazeエンドポイントのうち5件が実際のサンプルレスポンスを、5件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
ドキュメント化されたエラー
TheBlazeのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
エージェントから呼べるMCPツール
TheBlazeのエンドポイントは5個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
統合前にAPIで収集できるデータを把握
1エンドポイント
Article
/theblaze/article
GETapiKey
1エンドポイント
Author
/theblaze/author
GETapiKey
1エンドポイント
Headlines
/theblaze/headlines
GETapiKey
1エンドポイント
News
/theblaze/news
GETapiKey
1エンドポイント
Sections
/theblaze/sections
GETapiKey
エンドポイントカタログ
TheBlaze APIエンドポイント
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ツール 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ツール 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ツール 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ツール 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ツール theblaze_sections
x-api-key:header
関連API
メディア・ストリーミングのその他のカバレッジ
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.
TheBlazeのスクレイピング方法
5ステップでTheBlazeのデータを抽出
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/
- ステップ 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.
- ステップ 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.
- ステップ 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.
- ステップ 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.
- ステップ 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
TheBlazeのスクレイピング：よくある質問
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.