Monitor South African reporting across 23 editorial desks
Use TimesLIVE endpoints to turn monitor south african reporting across 23 editorial desks into repeatable API requests with documented inputs and JSON responses.
翻译进行中。 该页面的简体中文翻译正在准备中，暂时以英文内容显示。
媒体与流媒体4 active endpointsapiKey
TimesLIVE API
South African reporting across 23 editorial desks, including national, regional, business, sport, and opinion coverage. Choose a verified editorial slug from the section list and retain it with each headline pull. Arc feeds support offset paging upstream, but the public API only accepts a section, so use repeated calls only where the API documentation permits and do not represent them as page-controlled. Podcasts are a separate product.
Collect South African reporting across 23 editorial desks, including national, regional, business, sport, and opinion coverage with documented TimesLIVE.
Endpoint families
4
Documented params
6
Examples
4
Live catalog snapshot
TimesLIVE coverage
Active endpoints
4
Methods
GET
Required params
6
Schema refs
4
Article1
Headlines1
News1
Sections1
{
"platform": "TimesLIVE",
"endpoint": "timeslive-sections",
"method": "GET",
"path": "/timeslive/sections",
"auth": "apiKey"
}Use cases
Workflows that fit TimesLIVE
Collect South African reporting across 23 editorial desks, including national, regional, business, sport, and opinion coverage with documented TimesLIVE.
Separate TimesLIVE feed records from article or profile follow-up
Use TimesLIVE endpoints to turn separate timeslive 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 TimesLIVE 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 TimesLIVE endpoint catalog — 4 endpoints, 6 documented request parameters, and 4 published response schemas — the same catalog Docs and Playground run against.
Documented endpoint coverage
4 documented TimesLIVE endpoints, grouped into 4 request families — Article, Headlines and News, plus 1 more.
Published request surface
6 request parameters are documented across those TimesLIVE endpoints, 6 of them required — the full input contract is public before you write any integration code.
Known response shape
4 of the 4 TimesLIVE endpoints ship a recorded example response, and 4 carry a documented response schema — you can code against the real JSON before the first request.
Documented failure modes
TimesLIVE 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.
Agent-callable MCP tools
4 hosted MCP tools back the TimesLIVE 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
/timeslive/article
GETapiKey
1 endpoints
Headlines
/timeslive/headlines
GETapiKey
1 endpoints
News
/timeslive/news
GETapiKey
1 endpoints
Sections
/timeslive/sections
GETapiKey
Endpoint catalog
TimesLIVE API endpoints
GETapiKeyexample
/timeslive/articleGet TimesLIVE article content
Returns article metadata and body paragraphs for a canonical TimesLIVE editorial article URL. Some stories may have a publisher access gate; paywalled is set when the page's first-party access flags indicate restricted content.
MCP tool timeslive_article
url:queryx-api-key:header
GETapiKeyexample
/timeslive/headlinesGet TimesLIVE section headlines
Returns current TimesLIVE stories for a section. Pass a slug from timeslive_sections; results are the first 15 items in the live section order.
MCP tool timeslive_headlines
section:queryx-api-key:header
GETapiKeyexample
/timeslive/newsGet TimesLIVE top stories
Returns current TimesLIVE stories, including section-specific headlines. Article access can vary by story.
MCP tool timeslive_news
x-api-key:header
GETapiKeyexample
/timeslive/sectionsGet TimesLIVE sections
Returns the complete public editorial navigation set accepted by the TimesLIVE headlines endpoint. External Sunday Times, partner, podcast, account, and link-only surfaces are excluded.
MCP tool timeslive_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 TimesLIVE
Extract TimesLIVE data in 4 steps
TimesLIVE is South African reporting across 23 editorial desks, including national, regional, business, sport, and opinion coverage. A live /timeslive/sections response on 2026-10-14 contained 23 section records; refresh it before scheduling because publisher feeds change. Choose a verified editorial slug from the section list and retain it with each headline pull. Arc feeds support offset paging upstream, but the public API only accepts a section, so use repeated calls only where the API documentation permits and do not represent them as page-controlled. Podcasts are a separate product. Article text comes from public page paragraphs and premium/free markers are preserved when supplied. An absent marker is not proof that a story is subscriber-free; no author endpoint is available. Use the endpoint cards for this integration's accepted inputs. Publisher reference: https://www.timeslive.co.za/
- Step 1
Refresh TimesLIVE's editorial inventory
A live /timeslive/sections response on 2026-10-14 contained 23 section records; refresh it before scheduling because publisher feeds change. Choose a verified editorial slug from the section list and retain it with each headline pull. Arc feeds support offset paging upstream, but the public API only accepts a section, so use repeated calls only where the API documentation permits and do not represent them as page-controlled. Podcasts are a separate product.
- Step 2
Plan around TimesLIVE's source-specific constraints
The 23 editorial desks can focus a headline pull, but upstream offset support does not create a Crawlora page parameter. Keep premium/free markers and publication timestamps when returned; absence of a premium marker is not evidence of open access.
- Step 3
Carry TimesLIVE section context into each headline pull
The 23 editorial desks can focus a headline pull, but upstream offset support does not create a Crawlora page parameter. Keep premium/free markers and publication timestamps when returned; absence of a premium marker is not evidence of open access. Pass only a value returned by /timeslive/sections and accepted by /timeslive/headlines; preserve the selected desk with its results.
- Step 4
Check TimesLIVE article access before using body text
Article text comes from public page paragraphs and premium/free markers are preserved when supplied. An absent marker is not proof that a story is subscriber-free; no author endpoint is available. Keep teaser, truncation, premium, or access fields beside the canonical URL so downstream users can see what the publisher actually returned.
FAQ
Scraping TimesLIVE: common questions
How should I scope a TimesLIVE headline pull?
A live /timeslive/sections response on 2026-10-14 contained 23 section records; refresh it before scheduling because publisher feeds change. Choose a verified editorial slug from the section list and retain it with each headline pull. Arc feeds support offset paging upstream, but the public API only accepts a section, so use repeated calls only where the API documentation permits and do not represent them as page-controlled. Podcasts are a separate product.
What should I preserve when using TimesLIVE's article route?
Article text comes from public page paragraphs and premium/free markers are preserved when supplied. An absent marker is not proof that a story is subscriber-free; no author endpoint is available.
What should a collector avoid assuming about TimesLIVE?
Choose a verified editorial slug from the section list and retain it with each headline pull. Arc feeds support offset paging upstream, but the public API only accepts a section, so use repeated calls only where the API documentation permits and do not represent them as page-controlled. Podcasts are a separate product. Article text comes from public page paragraphs and premium/free markers are preserved when supplied. An absent marker is not proof that a story is subscriber-free; no author endpoint is available.