Monitor ScienceAlert's science reporting across Space
Use ScienceAlert endpoints to turn monitor sciencealert's science reporting across space into repeatable API requests with documented inputs and JSON responses.
翻译进行中。 该页面的简体中文翻译正在准备中，暂时以英文内容显示。
媒体与流媒体5 active endpointsapiKey
ScienceAlert API
ScienceAlert's science reporting across Space, Health, Environment, Humans, Tech, Nature, Physics, and This Week in Science. Use the eight exact navigation sections to keep research monitoring focused, and open canonical story URLs for publicly available article paragraphs. Author URLs return profile metadata plus one recent-article page, which is useful for contributor context but not a complete archive.
Collect ScienceAlert's science reporting across Space, Health, Environment, Humans, Tech, Nature, Physics, and This Week in Science with documented.
Endpoint families
5
Documented params
8
Examples
5
Live catalog snapshot
ScienceAlert coverage
Active endpoints
5
Methods
GET
Required params
8
Schema refs
5
Article1
Author1
Headlines1
News1
{
"platform": "ScienceAlert",
"endpoint": "sciencealert-sections",
"method": "GET",
"path": "/sciencealert/sections",
"auth": "apiKey"
}Use cases
Workflows that fit ScienceAlert
Collect ScienceAlert's science reporting across Space, Health, Environment, Humans, Tech, Nature, Physics, and This Week in Science with documented.
Separate ScienceAlert feed records from article or profile follow-up
Use ScienceAlert endpoints to turn separate sciencealert 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 ScienceAlert 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 ScienceAlert endpoint catalog — 5 endpoints, 8 documented request parameters, and 5 published response schemas — the same catalog Docs and Playground run against.
Documented endpoint coverage
5 documented ScienceAlert endpoints, grouped into 5 request families — Article, Author and Headlines, plus 2 more.
Published request surface
8 request parameters are documented across those ScienceAlert endpoints, 8 of them required — the full input contract is public before you write any integration code.
Known response shape
5 of the 5 ScienceAlert endpoints ship a recorded example response, and 5 carry a documented response schema — you can code against the real JSON before the first request.
Documented failure modes
ScienceAlert 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
5 hosted MCP tools back the ScienceAlert 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
/sciencealert/article
GETapiKey
1 endpoints
Author
/sciencealert/author
GETapiKey
1 endpoints
Headlines
/sciencealert/headlines
GETapiKey
1 endpoints
News
/sciencealert/news
GETapiKey
1 endpoints
Sections
/sciencealert/sections
GETapiKey
Endpoint catalog
ScienceAlert API endpoints
GETapiKeyexample
/sciencealert/articleGet ScienceAlert article content
Returns a ScienceAlert article by absolute canonical `url`: title, description, section, authors, publication and update times, image, the cleaned body `paragraphs` and a `paywalled` flag. Section pages and author listing URLs are rejected.
MCP tool sciencealert_article
url:queryx-api-key:header
GETapiKeyexample
/sciencealert/authorGet a ScienceAlert author profile
Returns a ScienceAlert author's profile and one page of articles, from an author listing `url` in the form `https://www.sciencealert.com/<author>/page/<number>`; the first observed page is `/page/0`. The response has the name, `slug`, biography, image, social links, that page's articles, and `page` and `has_next_page` for paging.
MCP tool sciencealert_author
url:queryx-api-key:header
GETapiKeyexample
/sciencealert/headlinesGet ScienceAlert section headlines
Returns the latest ScienceAlert stories for one section. `section` is required and takes `space`, `health`, `environment`, `humans`, `tech`, `nature`, `physics` or `this-week-in-science`; other values are rejected. Each item has its title and URL.
MCP tool sciencealert_headlines
section:queryx-api-key:header
GETapiKeyexample
/sciencealert/newsGet ScienceAlert top stories
Returns ScienceAlert's latest top stories across the site. Takes no parameters, and `sciencealert-headlines` narrows by section instead. Each item has its title, URL, summary, author and publication time.
MCP tool sciencealert_news
x-api-key:header
GETapiKeyexample
/sciencealert/sectionsGet ScienceAlert sections
Lists the eight top-level ScienceAlert sections that `sciencealert-headlines` accepts: `space`, `health`, `environment`, `humans`, `tech`, `nature`, `physics` and `this-week-in-science`. Each entry has a `slug`, a display `name` and the section page `url`.
MCP tool sciencealert_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 ScienceAlert
Extract ScienceAlert data in 5 steps
ScienceAlert is ScienceAlert's science reporting across Space, Health, Environment, Humans, Tech, Nature, Physics, and This Week in Science. A live /sciencealert/sections response on 2026-10-14 contained 8 section records; refresh it before scheduling because publisher feeds change. Use the eight exact navigation sections to keep research monitoring focused, and open canonical story URLs for publicly available article paragraphs. Author URLs return profile metadata plus one recent-article page, which is useful for contributor context but not a complete archive. Section pagination was not validated and produced an access error in testing; the API exposes no page parameter. Do not promise complete archives or bypass publisher access controls. Use the endpoint cards for this integration's accepted inputs. Publisher reference: https://www.sciencealert.com/
- Step 1
Refresh ScienceAlert's editorial inventory
A live /sciencealert/sections response on 2026-10-14 contained 8 section records; refresh it before scheduling because publisher feeds change. Use the eight exact navigation sections to keep research monitoring focused, and open canonical story URLs for publicly available article paragraphs. Author URLs return profile metadata plus one recent-article page, which is useful for contributor context but not a complete archive.
- Step 2
Plan around ScienceAlert's source-specific constraints
Record the exact section slug returned by discovery before creating a scheduled feed pull. The article route and public contributor profiles are distinct lookups; no caller-controlled archive page was validated, so do not derive paging from buttons on the website.
- Step 3
Carry ScienceAlert section context into each headline pull
Record the exact section slug returned by discovery before creating a scheduled feed pull. The article route and public contributor profiles are distinct lookups; no caller-controlled archive page was validated, so do not derive paging from buttons on the website. Pass only a value returned by /sciencealert/sections and accepted by /sciencealert/headlines; preserve the selected desk with its results.
- Step 4
Check ScienceAlert article access before using body text
Section pagination was not validated and produced an access error in testing; the API exposes no page parameter. Do not promise complete archives or bypass publisher access controls. Keep teaser, truncation, premium, or access fields beside the canonical URL so downstream users can see what the publisher actually returned.
- Step 5
Use ScienceAlert's contributor route for its documented purpose
Use the eight exact navigation sections to keep research monitoring focused, and open canonical story URLs for publicly available article paragraphs. Author URLs return profile metadata plus one recent-article page, which is useful for contributor context but not a complete archive. Section pagination was not validated and produced an access error in testing; the API exposes no page parameter. Do not promise complete archives or bypass publisher access controls.
FAQ
Scraping ScienceAlert: common questions
How should I scope a ScienceAlert headline pull?
A live /sciencealert/sections response on 2026-10-14 contained 8 section records; refresh it before scheduling because publisher feeds change. Use the eight exact navigation sections to keep research monitoring focused, and open canonical story URLs for publicly available article paragraphs. Author URLs return profile metadata plus one recent-article page, which is useful for contributor context but not a complete archive.
What should I preserve when using ScienceAlert's article route?
Section pagination was not validated and produced an access error in testing; the API exposes no page parameter. Do not promise complete archives or bypass publisher access controls.
Can ScienceAlert articles be paged by an archive button?
The publisher page may expose more-story controls, but the validated public contract does not offer an archive page input. Use a returned section slug for headlines and canonical URLs for article requests; do not infer a stable page cursor from browser behavior. Contributor profiles are a separate route and should be resolved from a verified profile URL, not from a guessed author-name search.