Monitor Israeli news reporting and analysis with regional
Jerusalem Postエンドポイントを使えば、「Monitor Israeli news reporting and analysis with regional」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
翻訳作業中です。 日本語訳を準備中のため、このページは一時的に英語で表示されます。
メディア・ストリーミング稼働中エンドポイント 6件apiKey
Jerusalem Post API
Israeli news reporting and analysis with regional, world, and specialist editorial sections. Start from the supported RSS-derived section list, then use a canonical story URL when a headline merits closer review. The author directory and profile route cover person pages and bloggers under their documented URL forms, which helps distinguish a profile lookup from a search for a byline.
Collect Israeli news reporting and analysis with regional, world, and specialist editorial sections with documented Jerusalem Post routes.
エンドポイントファミリー
6
ドキュメント化されたパラメータ
9
サンプル数
6
ライブカタログスナップショット
Jerusalem Postのカバレッジ
稼働エンドポイント
6
メソッド
GET
必須パラメータ
9
スキーマ参照
6
Article1
Author1
Authors1
Headlines1
{
"platform": "Jerusalem Post",
"endpoint": "jerusalempost-sections",
"method": "GET",
"path": "/jerusalempost/sections",
"auth": "apiKey"
}ユースケース
Jerusalem Postに適したワークフロー
Collect Israeli news reporting and analysis with regional, world, and specialist editorial sections with documented Jerusalem Post routes.
Separate Jerusalem Post feed records from article or profile follow-up
Jerusalem Postエンドポイントを使えば、「Separate Jerusalem Post feed records from article or profile follow-up」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Preserve source URLs, dates, and access outcomes for review
Jerusalem Postエンドポイントを使えば、「Preserve source URLs, dates, and access outcomes for review」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
Crawloraによるこのプラットフォームの処理方法
以下の数値はすべて、稼働中のJerusalem Postエンドポイントカタログから取得しています（エンドポイント6件、ドキュメント化されたリクエストパラメータ9個、公開レスポンススキーマ6件）。DocsとPlaygroundが参照しているカタログと同じものです。
ドキュメント化されたエンドポイント
Jerusalem Postのエンドポイントは6件、6つのリクエストファミリーに分類されています（Article、Author、Authorsほか3件）。
公開されたリクエスト仕様
これらのJerusalem Postエンドポイントには9個のリクエストパラメータがドキュメント化されており、うち9個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
判明しているレスポンス構造
6件のJerusalem Postエンドポイントのうち6件が実際のサンプルレスポンスを、6件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
ドキュメント化されたエラー
Jerusalem Postのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
エージェントから呼べるMCPツール
Jerusalem Postのエンドポイントは6個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
統合前にAPIで収集できるデータを把握
1エンドポイント
Article
/jerusalempost/article
GETapiKey
1エンドポイント
Author
/jerusalempost/author
GETapiKey
1エンドポイント
Authors
/jerusalempost/authors
GETapiKey
1エンドポイント
Headlines
/jerusalempost/headlines
GETapiKey
1エンドポイント
News
/jerusalempost/news
GETapiKey
1エンドポイント
Sections
/jerusalempost/sections
GETapiKey
エンドポイントカタログ
Jerusalem Post APIエンドポイント
GETapiKeyexample
/jerusalempost/articleGet Jerusalem Post article content
Returns public Jerusalem Post article metadata and free body paragraphs. If isAccessibleForFree is false, paywalled is true and body paragraphs are omitted; paid article text is not represented by feed snippets.
MCPツール jerusalempost_article
url:queryx-api-key:header
GETapiKeyexample
/jerusalempost/authorGet Jerusalem Post author profile
Returns a Jerusalem Post author or blogger profile by `url`, a canonical `/author/<slug>` or `/blogger/<slug>` link. The response has the profile `type`, name, `description`, `image_url` and article cards with title, URL, summary and publication time.
MCPツール jerusalempost_author
url:queryx-api-key:header
GETapiKeyexample
/jerusalempost/authorsList Jerusalem Post author profiles
Returns the current author and blogger profile URLs discovered from the site's public Experts sitemap. This dynamic roster is intentionally exposed as a discovery endpoint.
MCPツール jerusalempost_authors
x-api-key:header
GETapiKeyexample
/jerusalempost/headlinesGet Jerusalem Post section headlines
Returns current Jerusalem Post stories for one section. `section` is required and takes one of 40 slugs such as `israel-news`, `iran-news`, `middle-east`, `tech-and-startups` or `torah-portion`. Each item has its title, URL, author, publication time and image, plus a summary except on premium items, which have none.
MCPツール jerusalempost_headlines
section:queryx-api-key:header
GETapiKeyexample
/jerusalempost/newsGet Jerusalem Post top stories
Returns recent Jerusalem Post front-page stories, with no parameters. Each item has its title, URL, author, publication time and image where available. Premium items keep their title and metadata but have no summary. Use `jerusalempost-article` to read an article and check its paywall flag.
MCPツール jerusalempost_news
x-api-key:header
GETapiKeyexample
/jerusalempost/sectionsGet Jerusalem Post section inventory
Lists the 40 English-language editorial sections accepted by `jerusalempost-headlines`, such as `world-news`, `israel-politics`, `archaeology` and `jewish-holidays`. Each entry has a `slug`, display `name` and section `url`. Takes no parameters.
MCPツール jerusalempost_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.
Jerusalem Postのスクレイピング方法
5ステップでJerusalem Postのデータを抽出
Jerusalem Post is Israeli news reporting and analysis with regional, world, and specialist editorial sections. A live /jerusalempost/sections response on 2026-10-14 contained 40 section records; refresh it before scheduling because publisher feeds change. Start from the supported RSS-derived section list, then use a canonical story URL when a headline merits closer review. The author directory and profile route cover person pages and bloggers under their documented URL forms, which helps distinguish a profile lookup from a search for a byline. Feed records include an isPremium flag. The article route reflects anonymous public access and must preserve premium/access indicators; a successful route does not mean subscriber-only text is available. Use the endpoint cards for this integration's accepted inputs. Publisher reference: https://www.jpost.com/rss/rssfeedsfrontpage.aspx
- ステップ 1
Refresh Jerusalem Post's editorial inventory
A live /jerusalempost/sections response on 2026-10-14 contained 40 section records; refresh it before scheduling because publisher feeds change. Start from the supported RSS-derived section list, then use a canonical story URL when a headline merits closer review. The author directory and profile route cover person pages and bloggers under their documented URL forms, which helps distinguish a profile lookup from a search for a byline.
- ステップ 2
Plan around Jerusalem Post's source-specific constraints
Retain the returned premium signal when present and treat it as part of each article record. The publisher has a contributor directory and profile route, but those profiles should not be mistaken for an endpoint that searches every byline string.
- ステップ 3
Carry Jerusalem Post section context into each headline pull
Retain the returned premium signal when present and treat it as part of each article record. The publisher has a contributor directory and profile route, but those profiles should not be mistaken for an endpoint that searches every byline string. Pass only a value returned by /jerusalempost/sections and accepted by /jerusalempost/headlines; preserve the selected desk with its results.
- ステップ 4
Check Jerusalem Post article access before using body text
Feed records include an isPremium flag. The article route reflects anonymous public access and must preserve premium/access indicators; a successful route does not mean subscriber-only text is available. Keep teaser, truncation, premium, or access fields beside the canonical URL so downstream users can see what the publisher actually returned.
- ステップ 5
Use Jerusalem Post's contributor route for its documented purpose
Start from the supported RSS-derived section list, then use a canonical story URL when a headline merits closer review. The author directory and profile route cover person pages and bloggers under their documented URL forms, which helps distinguish a profile lookup from a search for a byline. Feed records include an isPremium flag. The article route reflects anonymous public access and must preserve premium/access indicators; a successful route does not mean subscriber-only text is available.
FAQ
Jerusalem Postのスクレイピング：よくある質問
How should I scope a Jerusalem Post headline pull?
A live /jerusalempost/sections response on 2026-10-14 contained 40 section records; refresh it before scheduling because publisher feeds change. Start from the supported RSS-derived section list, then use a canonical story URL when a headline merits closer review. The author directory and profile route cover person pages and bloggers under their documented URL forms, which helps distinguish a profile lookup from a search for a byline.
What should I preserve when using Jerusalem Post's article route?
Feed records include an isPremium flag. The article route reflects anonymous public access and must preserve premium/access indicators; a successful route does not mean subscriber-only text is available.
How should I interpret Jerusalem Post premium fields?
Preserve a premium indicator when the response supplies one and attach it to the story record. A missing indicator does not establish that the article is free to read. Contributor directory and profile routes describe people; they do not search arbitrary byline strings.