Docs menu
Boston Globe API endpoint
Boston Globe top stories API
Returns recent Boston Globe story metadata and summaries. Article bodies, sections, headlines-by-section, and author profiles are not exposed, and some stories require a subscription.
GETapiKey1 credit/requestBoston Globepublicnews.newsResponseDoc
Boston Globe/bostonglobe/newsEndpoint facts
- Method
- GET
- API path
- /bostonglobe/news
- Auth
- apiKey
- Credits
- 1 credit/request
- Charged on
- Successful 2xx responses only
- Platform
- Boston Globe
- Response schema
- #/definitions/publicnews.newsResponseDoc
How this endpoint behaves
Returns current Boston Globe story metadata and short descriptions from its public Arc RSS feed. Each item may include a title, canonical URL, summary, publication time, byline, and lead image. The RSS feed also contains content:encoded article prose; this endpoint intentionally returns only the short RSS description and never exposes that full-body field.
There are no query parameters. This is the only Boston Globe route currently supported: the public feed inventory is not established well enough to expose sections or section headlines, and the site’s article pages include subscription gates, so article bodies and author pages are not returned.
Sampled response
- Request, 14 Oct 2026
- GET /bostonglobe/news
- Items in items
- 99
- Fields filled in every checked item
- 4
- Fields empty in some or all items
- 2
| Field | Filled in, of 99 checked | Values in the sample |
|---|---|---|
| title | 99 | median 81 characters |
| url | 99 | bostonglobe.com |
| summary | 99 | median 123 characters |
| published_at | 99 | 2026-09-25 to 2026-10-13 |
| author | 97 | |
| image_url | 91 | bostonglobe-bostonglobe-prod.web.arc-cdn.net |
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/bostonglobe/news" \ -H "x-api-key: $CRAWLORA_API_KEY"
Example JSON response
{
"code": 200,
"data": {
"items": [
{
"title": "Example Boston Globe headline",
"url": "https://www.bostonglobe.com/2026/09/28/metro/example-story",
"summary": "A short public description of the story.",
"published_at": "2026-09-28T14:00:00Z",
"author": "Example Reporter"
}
]
}
}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/bostonglobe/news" \
-H "x-api-key: $CRAWLORA_API_KEY"