Monitor South African public-interest journalism
Mit Daily Maverick-Endpunkten verwandelst du monitor south african public-interest journalism in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
South African public-interest journalism, investigations, opinion, and regional reporting. Use the section list to focus a monitor on a verified editorial category, and keep opinion pieces distinct from reported articles when reviewing results. The rolling news sitemap is useful for understanding discovery coverage, while the exposed headlines call itself accepts a section only.
Collect South African public-interest journalism, investigations, opinion, and regional reporting with documented Daily Maverick routes.
Endpunkt-Familien
4
Dokumentierte Parameter
6
Beispiele
4
Live-Katalog-Snapshot
Aktive Endpunkte
4
Methoden
GET
Pflichtparameter
6
Schema-Referenzen
4
{
"platform": "Daily Maverick",
"endpoint": "dailymaverick-sections",
"method": "GET",
"path": "/dailymaverick/sections",
"auth": "apiKey"
}Use Cases
Collect South African public-interest journalism, investigations, opinion, and regional reporting with documented Daily Maverick routes.
Mit Daily Maverick-Endpunkten verwandelst du monitor south african public-interest journalism in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Daily Maverick-Endpunkten verwandelst du separate daily maverick feed records from article or profile follow-up in wiederholbare API-Requests mit dokumentierten Inputs und JSON-Antworten.
Mit Daily Maverick-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-Daily Maverick-Endpunktkatalog — 4 Endpunkte, 6 dokumentierte Request-Parameter und 4 veröffentlichte Response-Schemas — demselben Katalog, gegen den auch Docs und Playground laufen.
4 documented Daily Maverick endpoints, grouped into 4 request families — Article, Headlines and News, plus 1 more.
6 request parameters are documented across those Daily Maverick endpoints, 6 of them required — the full input contract is public before you write any integration code.
4 of the 4 Daily Maverick endpoints ship a recorded example response, and 4 carry a documented response schema — you can code against the real JSON before the first request.
Daily Maverick endpoints document their error responses (400, 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.
4 hosted MCP tools back the Daily Maverick endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Abdeckungskarte
/dailymaverick/article
/dailymaverick/headlines
/dailymaverick/news
/dailymaverick/sections
Endpunktkatalog
/dailymaverick/articleExtracts the public article metadata and body paragraphs Daily Maverick serves to an anonymous visitor. The paywalled flag is set only when the page exposes the publisher's access-control marker.
MCP-Tool dailymaverick_article
/dailymaverick/headlinesReturns up to 21 current story cards for one Daily Maverick category. `section` is required and takes one of 51 slugs such as `maverick-news`, `business-maverick`, `opinionistas`, `politics` or `sport`. Each item has its title, URL and type, plus summary, publication time, author and image when the outlet provides them.
MCP-Tool dailymaverick_headlines
/dailymaverick/newsLists recent Daily Maverick articles and opinionista pieces from a rolling set of the newest entries. Each item has its title, URL, `type`, publication time and, when available, summary, author and image. Videos, cartoons and other non-article pages are excluded.
MCP-Tool dailymaverick_news
/dailymaverick/sectionsLists the 51 article-bearing Daily Maverick categories accepted by `dailymaverick-headlines`, such as `africa`, `maverick-citizen`, `op-eds` and `sci-tech`. Each entry has the `slug`, `name` and category `url`. Empty, media-only and other non-story categories are omitted; checked 2026-09-28.
MCP-Tool dailymaverick_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 Daily Maverick
Daily Maverick is South African public-interest journalism, investigations, opinion, and regional reporting. A live /dailymaverick/sections response on 2026-10-14 contained 51 section records; refresh it before scheduling because publisher feeds change. Use the section list to focus a monitor on a verified editorial category, and keep opinion pieces distinct from reported articles when reviewing results. The rolling news sitemap is useful for understanding discovery coverage, while the exposed headlines call itself accepts a section only. The article route accepts canonical /article/ and /opinionista/ URLs, but returned text can be a teaser and a paywall marker is meaningful when present. Although the upstream source pages use paging, Crawlora's section route has no page parameter; author profiles were not verified. Use the endpoint cards for this integration's accepted inputs. Publisher reference: https://www.dailymaverick.co.za/
A live /dailymaverick/sections response on 2026-10-14 contained 51 section records; refresh it before scheduling because publisher feeds change. Use the section list to focus a monitor on a verified editorial category, and keep opinion pieces distinct from reported articles when reviewing results. The rolling news sitemap is useful for understanding discovery coverage, while the exposed headlines call itself accepts a section only.
Separate reported pieces from Opinionista URLs in your records because the publisher exposes both paths and access can differ. Its website sitemap has paging, but the Crawlora section-headlines call does not accept a page input; do not manufacture a cursor from upstream behavior.
Separate reported pieces from Opinionista URLs in your records because the publisher exposes both paths and access can differ. Its website sitemap has paging, but the Crawlora section-headlines call does not accept a page input; do not manufacture a cursor from upstream behavior. Pass only a value returned by /dailymaverick/sections and accepted by /dailymaverick/headlines; preserve the selected desk with its results.
The article route accepts canonical /article/ and /opinionista/ URLs, but returned text can be a teaser and a paywall marker is meaningful when present. Although the upstream source pages use paging, Crawlora's section route has no page parameter; author profiles were not verified. Keep teaser, truncation, premium, or access fields beside the canonical URL so downstream users can see what the publisher actually returned.
FAQ
A live /dailymaverick/sections response on 2026-10-14 contained 51 section records; refresh it before scheduling because publisher feeds change. Use the section list to focus a monitor on a verified editorial category, and keep opinion pieces distinct from reported articles when reviewing results. The rolling news sitemap is useful for understanding discovery coverage, while the exposed headlines call itself accepts a section only.
The article route accepts canonical /article/ and /opinionista/ URLs, but returned text can be a teaser and a paywall marker is meaningful when present. Although the upstream source pages use paging, Crawlora's section route has no page parameter; author profiles were not verified.
The publisher site has upstream paging, but the Crawlora headlines contract exposes a section selector without a page field. A scheduled collector should treat each call as the available section result and retain collection time; it cannot promise historical pages by incrementing a guessed parameter.