Progressive commentary analysis
Use Salon endpoints to turn progressive commentary analysis into repeatable API requests with documented inputs and JSON responses.
Salon is a progressive US news and commentary magazine. Follow politics, culture, food, health, science, and opinion coverage through structured public feeds and article records for progressive commentary analysis.
Extract politics, culture, science, health, and long-form commentary from Salon with structured article, section, headline, news, and author data.
Endpoint families
5
Documented params
8
Examples
5
Live catalog snapshot
Active endpoints
5
Methods
GET
Required params
8
Schema refs
5
{
"platform": "Salon",
"endpoint": "salon-news",
"method": "GET",
"path": "/salon/news",
"auth": "apiKey"
}Use cases
Extract politics, culture, science, health, and long-form commentary from Salon with structured article, section, headline, news, and author data.
Use Salon endpoints to turn progressive commentary analysis into repeatable API requests with documented inputs and JSON responses.
Use Salon endpoints to turn salon section and headline tracking into repeatable API requests with documented inputs and JSON responses.
Use Salon endpoints to turn article and byline research for culture researchers and us media analysts into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Salon endpoint catalog — 5 endpoints, 8 documented request parameters, and 5 published response schemas — the same catalog Docs and Playground run against.
5 documented Salon endpoints, grouped into 5 request families — Article, Author and Headlines, plus 2 more.
8 request parameters are documented across those Salon endpoints, 8 of them required — the full input contract is public before you write any integration code.
5 of the 5 Salon endpoints ship a recorded example response, and 5 carry a documented response schema — you can code against the real JSON before the first request.
Salon 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.
5 hosted MCP tools back the Salon endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/salon/article
/salon/author
/salon/headlines
/salon/news
/salon/sections
Endpoint catalog
/salon/articleReturns a Salon article by canonical `url` on `www.salon.com` in the `/YYYY/MM/DD/<slug>/` form: title, description, section, authors, publication and update times, image, body `paragraphs` and a `paywalled` flag.
Sampled 14 Oct 2026: 8 of 8 fields returned with a value. published_at: 2026-09-23; section: “All Salon, News & Politics”.
MCP tool salon_article
/salon/authorReturns a Salon writer's profile by canonical `url` (`https://www.salon.com/writer/<slug>`): name, `job_title`, `bio`, `image_url`, `same_as` links and a list of articles. Each article carries only a title and URL, with no date or category. Job title, photo and `same_as` appear only when the writer page shows them.
Sampled 14 Oct 2026: 24 items, 2 fields filled in every item. url: salon.com; title: median 44 characters.
MCP tool salon_author
/salon/headlinesReturns the latest Salon stories for one section. `section` is required and takes one of 32 slugs, including `home`, `news-and-politics`, `politics`, `opinion`, `culture`, `science-and-health` and `technology`. Each item has its title, URL, summary, publication time, author and image.
Sampled 14 Oct 2026: 30 items, 6 fields filled in every item. published_at: 2026-10-04 to 2026-10-13; url: salon.com.
MCP tool salon_headlines
/salon/newsReturns Salon's latest top stories across the site. Takes no parameters, and `salon-headlines` narrows by section instead. Each item has its title, URL, summary, publication time, author and image.
Sampled 14 Oct 2026: 30 items, 6 fields filled in every item. published_at: 2006-05-03 to 2026-10-13; url: salon.com.
MCP tool salon_news
/salon/sectionsLists the 32 Salon sections that `salon-headlines` accepts, from `home` and `news-and-politics` to `working_ahead`. Each entry has a `slug`, a display `name` and the section's feed `url`. The list includes older event slugs such as `oscars_2012` and `sxsw_2013`.
Sampled 14 Oct 2026: 32 items, 3 fields filled in every item. name: “Home” and 31 other values; url: salon.com.
MCP tool salon_sections
Related 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.
How to scrape Salon
Salon is a US progressive news and commentary magazine whose public editorial mix spans politics, culture, food, health, and science. A monitoring project should separate reported developments from analysis and opinion, because a contributor's interpretation is not the same thing as the underlying event. Its named sections and bylines supply the context needed to study how a topic moves from policy debate into cultural commentary. On 2026-10-25 the documented section list held 32 slugs, and not all are live: oscars_2012 returned 30 items, the newest published 2018-03-13, and the list also keeps sxsw_2013. A section slug is a feed tag that outlived its event, so check the newest date before you rely on it.
Call /salon/sections, then request /salon/headlines for the slug you need and read the newest published_at. The oscars_2012 feed ran from 2017-01-24 to 2018-03-13 and mixed Oscar coverage with a Twitter-bot exposé, an ICE spokesman's resignation and a Fox News host's vacation, so the slug names a tag, not a topic.
The list separates news-and-politics, politics and the_brief from opinion, satire and life-stories. Pull them as separate feeds and carry the slug into your record; a satire piece in a news corpus will otherwise read as a claim.
Use /salon/news for the current stream and home for the front page. Store a collection timestamp with every headline, since the same piece can sit in several slugs and a front page rewrites itself.
Pass a canonical public URL to /salon/article for text and /salon/author for the named contributor when available. Salon URLs embed the publication date (/2018/03/13/...), which gives you a second date to reconcile with published_at.
Agent skills
Install a Crawlora agent skill and your agent can pull Salon data as JSON through the documented API, without writing a scraper. These skills cover Salon:
Researches public news from international, regional, business, technology, sports, science, and entertainment publishers through the Crawlora API —…
npx skills add github.com/Crawlora-org/crawlora-skills --skill news-media-researchFAQ
Event-era slugs such as oscars_2012 and sxsw_2013 are the likely candidates. oscars_2012 returned 30 items on 2026-10-25, the newest from 2018-03-13. Check the newest date per slug before including it in a monitor.
No. The oscars_2012 feed included a Russian-bot story, an ICE resignation and a TV-host vacation. Classify from the article text and keep the slug only as the feed it came from.
Pull satire as its own slug and label it at ingest, then exclude it from event counts. Do the same for opinion, because a contributor's interpretation is not the underlying event.