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
3
Documented params
5
Examples
0
Live catalog snapshot
Active endpoints
3
Methods
GET
Required params
4
Schema refs
3
{
"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 — 3 endpoints, 5 documented request parameters, and 3 published response schemas — the same catalog Docs and Playground run against.
3 documented Los Angeles Times endpoints, grouped into 3 request families — Article, Headlines and Sections.
5 request parameters are documented across those Los Angeles Times endpoints, 4 of them required — the full input contract is public before you write any integration code.
3 of the 3 Los Angeles Times endpoints carry a documented response schema, so the JSON shape is known before you write any parsing code.
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.
3 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/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/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
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.
Media & Streaming
Search public Ticketmaster events and browse the full discovery hierarchy by category or city, with pagination plus event, attraction, and venue detail endpoints -- including fan reviews, related attractions, trending attractions, and enhanced venue branding -- for live-entertainment research.
How to scrape Los Angeles Times
Crawlora exposes Los Angeles Times section discovery, section headline feeds, and full public article extraction with one API key.
Call /latimes/sections for current section values.
Pass a section to /latimes/headlines.
Pass a canonical latimes.com URL to /latimes/article.
FAQ
Call /latimes/sections and use a returned slug with /latimes/headlines. This keeps clients aligned with the publisher's current public section navigation.
The endpoint returns the selected section and its current story cards as normalized records, including headline, URL, summary, publication metadata, and image data when the source provides it.
A canonical article URL returns the published metadata and ordered public body paragraphs, with upstream blocks or unexpected templates surfaced as errors instead of a misleading empty success.
No account, subscription cookie, or stored browser session is used. Crawlora fetches credential-free public news pages through the production scraper transport and protects each normalized public API call with your Crawlora API key.