Monitor Israeli news reporting and analysis with regional
Mit Jerusalem Post-Endpunkten verwandelst du monitor israeli news reporting and analysis with regional in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
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.
Endpunkt-Familien
6
Dokumentierte Parameter
9
Beispiele
6
Live-Katalog-Snapshot
Aktive Endpunkte
6
Methoden
GET
Pflichtparameter
9
Schema-Referenzen
6
{
"platform": "Jerusalem Post",
"endpoint": "jerusalempost-sections",
"method": "GET",
"path": "/jerusalempost/sections",
"auth": "apiKey"
}Use Cases
Collect Israeli news reporting and analysis with regional, world, and specialist editorial sections with documented Jerusalem Post routes.
Mit Jerusalem Post-Endpunkten verwandelst du monitor israeli news reporting and analysis with regional in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Jerusalem Post-Endpunkten verwandelst du separate jerusalem post feed records from article or profile follow-up in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Jerusalem Post-Endpunkten verwandelst du preserve source urls, dates, and access outcomes for review in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Managed Execution
Jede Zahl unten stammt direkt aus dem Live-Jerusalem Post-Endpunktkatalog — 6 Endpunkte, 9 dokumentierte Request-Parameter und 6 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
6 documented Jerusalem Post endpoints, grouped into 6 request families — Article, Author and Authors, plus 3 more.
9 request parameters are documented across those Jerusalem Post endpoints, 9 of them required — the full input contract is public before you write any integration code.
6 of the 6 Jerusalem Post endpoints ship a recorded example response, and 6 carry a documented response schema — you can code against the real JSON before the first request.
Jerusalem Post 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.
6 hosted MCP tools back the Jerusalem Post endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
/jerusalempost/article
/jerusalempost/author
/jerusalempost/authors
/jerusalempost/headlines
/jerusalempost/news
/jerusalempost/sections
Endpunktkatalog
/jerusalempost/articleReturns 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-Tool jerusalempost_article
/jerusalempost/authorReturns 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-Tool jerusalempost_author
/jerusalempost/authorsReturns 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-Tool jerusalempost_authors
/jerusalempost/headlinesReturns 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-Tool jerusalempost_headlines
/jerusalempost/newsReturns 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-Tool jerusalempost_news
/jerusalempost/sectionsLists 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-Tool jerusalempost_sections
Verwandte APIs
Media & Streaming
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
Browse Sportskeeda's sports and entertainment coverage, community wikis, quizzes, and fan games with the catalog's current slugs and filter limits.
Media & Streaming
Research streaming catalogs, title availability, providers, offers, seasons, episodes, and release changes from JustWatch with normalized JSON.
So scrapst du 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
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.
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.
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.
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.
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
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.
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.