Local news monitoring
Use Los Angeles Times endpoints to turn local news monitoring into repeatable API requests with documented inputs and JSON responses.
Turn Los Angeles Times sections and articles into structured JSON for local news monitoring, research, and aggregation.
Discover Los Angeles Times sections and get section headlines or full article content as structured JSON.
Endpoint families
4
Documented params
7
Examples
4
Live catalog snapshot
Active endpoints
4
Methods
GET
Required params
6
Schema refs
4
{
"platform": "Los Angeles Times",
"endpoint": "latimes-article",
"method": "GET",
"path": "/latimes/article",
"auth": "apiKey"
}Use cases
Discover Los Angeles Times sections and get section headlines or full article content as structured JSON.
Use Los Angeles Times endpoints to turn local news monitoring into repeatable API requests with documented inputs and JSON responses.
Use Los Angeles Times endpoints to turn media research into repeatable API requests with documented inputs and JSON responses.
Use Los Angeles Times endpoints to turn content aggregation into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Los Angeles Times endpoint catalog — 4 endpoints, 7 documented request parameters, and 4 published response schemas — the same catalog Docs and Playground run against.
4 documented Los Angeles Times endpoints, grouped into 4 request families — Article, Author and Headlines, plus 1 more.
7 request parameters are documented across those Los Angeles Times endpoints, 6 of them required — the full input contract is public before you write any integration code.
4 of the 4 Los Angeles Times endpoints ship a recorded example response, and 4 carry a documented response schema — you can code against the real JSON before the first request.
Los Angeles Times 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 Los Angeles Times endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/latimes/article
/latimes/author
/latimes/headlines
/latimes/sections
Endpoint catalog
/latimes/articleReturns a Los Angeles Times article's public metadata and body paragraphs from a canonical article URL, read from the page's NewsArticle structured data.
MCP tool latimes_article
/latimes/authorReturns a Los Angeles Times author's byline metadata, biography, contact/social links, and recent articles from a canonical author URL.
MCP tool latimes_author
/latimes/headlinesReturns fresh headlines from a public Los Angeles Times section RSS feed: title, canonical URL, summary, author, publication time, and lead image. section defaults to main.
MCP tool latimes_headlines
/latimes/sectionsReturns the complete set of section slugs accepted by latimes-headlines, each with its display name and public RSS feed URL.
MCP tool latimes_sections
Related APIs
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.
Media & Streaming
Turn Apple Books ebook and audiobook pages into structured data — search, catalog detail, paginated customer reviews, similar titles, author bibliographies, series listings, and chart rankings as normalized JSON. Credential-free.
How to scrape Los Angeles Times
The Los Angeles Times' public RSS layer covers 44 sections, from statewide news down to single-team feeds like Dodgers and Lakers, plus two Spanish-language verticals. A 2026-09-24 pull of the California section returned 93 stories in a single page. Crawlora's four LA Times endpoints turn that section directory, section headlines, full articles, and reporter byline pages into normalized JSON, with the Times' own is_accessible_for_free flag passed through on every article.
/latimes/sections returns all 44 section slugs and their public RSS feed URLs, from california and politics down to sports/dodgers and espanol/mexico.
Pass a slug to /latimes/headlines for that section's current RSS items. The california section returned 93 stories in a single 2026-09-24 pull, each with a single comma-joined author string per item, such as "Kate Sequeira, Ava Hu", rather than a list.
/latimes/article returns an authors array (unlike headlines' single string), section, published and updated timestamps, body paragraphs, and the is_accessible_for_free value the Times declares in its own structured data.
Pass a canonical latimes.com/people/<slug> URL to /latimes/author for that reporter's bio, job title, and recent articles; two of ten recent-article entries in one 2026-09-24 test omitted the summary field.
FAQ
44 on 2026-09-24, including sport-specific feeds like Dodgers, Lakers, and USC and two full Spanish-language sections. Call /latimes/sections rather than hardcoding a list, since the Times adds and retires feeds.
No. /latimes/headlines returns one comma-joined author string per story, like "Kate Sequeira, Ava Hu", while /latimes/article returns the same names as a proper array — build for both shapes if your integration reads both endpoints.
It is the Times' own declaration from the article's structured data, passed through unchanged, so you can tell which stories the paper marks as free and which it counts toward its meter. Crawlora reads the public article page only; it never signs in as a subscriber.
A canonical latimes.com/people/<slug> page, such as latimes.com/people/kate-sequeira — that's the Times' own reporter-bio URL structure, not a byline link pulled directly off an article page.
Biotech entrepreneur Patrick Soon-Shiong, who bought it for $500 million in 2018 and has said he plans to eventually take the paper public. These endpoints read the paper's existing public and metered pages as published, independent of that ownership.