Docs menu
Popular Mechanics API endpoint
Popular Mechanics top stories API
Returns current stories from Popular Mechanics' public all-stories RSS feed. Summaries are publisher teasers, not full article text. This feed-only route does not claim a complete section taxonomy or retrieve article bodies.
GETapiKey1 credit/requestPopular Mechanicspublicnews.newsResponseDoc
Popular Mechanics/popularmechanics/newsEndpoint facts
- Method
- GET
- API path
- /popularmechanics/news
- Auth
- apiKey
- Credits
- 1 credit/request
- Charged on
- Successful 2xx responses only
- Platform
- Popular Mechanics
- Response schema
- #/definitions/publicnews.newsResponseDoc
How this endpoint behaves
Query parameters: none.
Returns current stories from Popular Mechanics' public all-stories RSS feed. Items include a title and canonical URL and may include a publisher teaser summary and publication time. Summaries are publisher teasers, not full article text. This route is limited to the verified feed; it does not expose a complete section taxonomy or retrieve article bodies.
Workflow check
Start from the checked request: GET /popularmechanics/news. Live check on 2026-10-14: 50 items returned. Fields present in every checked item: title, url, summary, published_at, image_url.
Live monitoring
- Monitored request
- GET /popularmechanics/news
- Checks passed, 7 days to 14 Oct 2026
- 100%
- Median response time
- 1.63 s
Sampled response
- Request, 14 Oct 2026
- GET /popularmechanics/news
- Items in items
- 50
- Fields filled in every checked item
- 5
| Field | Filled in, of 50 checked | Values in the sample |
|---|---|---|
| title | 50 | median 79 characters |
| url | 50 | popularmechanics.com |
| summary | 50 | median 99 characters |
| published_at | 50 | 2026-10-09 to 2026-10-13 |
| image_url | 50 | hips.hearstapps.com |
Request parameters
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| x-api-key (header) | string | Yes | API key required |
cURL example
curl -X GET "https://api.crawlora.net/api/v1/popularmechanics/news" \ -H "x-api-key: $CRAWLORA_API_KEY"
Illustrative JSON response shape
{
"data": {
"items": [
{
"title": "A Popular Mechanics story",
"url": "https://www.popularmechanics.com/science/example-story/",
"summary": "A short publisher teaser.",
"published_at": "2026-09-28T14:00:00Z"
}
]
}
}Request schema
No body schema
Response schema
#/definitions/publicnews.newsResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| data | newsplatform.NewsResponse | No | ||||
| data.items | array | No | ||||
| data.items[].author | string | No | ||||
| data.items[].image_url | string | No | ||||
| data.items[].published_at | string | No | ||||
| data.items[].summary | string | No | ||||
| data.items[].title | string | No | ||||
| data.items[].type | string | No | ||||
| data.items[].url | string | No |
Failure responses
| Status | Description | Schema |
|---|---|---|
| 429 | Too Many Requests | #/definitions/app.Response |
| 503 | Service Unavailable | #/definitions/app.Response |
Code examples
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/popularmechanics/news" \
-H "x-api-key: $CRAWLORA_API_KEY"