Docs menu
PhoneArena API endpoint
PhoneArena sections API
Lists the three PhoneArena listings that `phonearena-headlines` accepts: `news` (the last two days of news), `news-month` (the newest news of the current calendar month) and `reviews` (the newest reviews, comparisons and hands-on articles of the current year). Each entry has a `slug`, a display `name` and a source `url`.
GETapiKey1 credit/requestPhoneArenapublicnews.sectionsResponseDoc
PhoneArena/phonearena/sectionsEndpoint facts
- Method
- GET
- API path
- /phonearena/sections
- Auth
- apiKey
- Credits
- 1 credit/request
- Charged on
- Successful 2xx responses only
- Platform
- PhoneArena
- Response schema
- #/definitions/publicnews.sectionsResponseDoc
How this endpoint behaves
Returns the public PhoneArena listings accepted by phonearena-headlines. Each entry has a slug, a display name, and the public sitemap url it is built from. The accepted slugs are:
news: the last two days of news stories (Google News sitemap), with exact titles and publication times.news-month: the newest news stories of the current calendar month (US Central time; in the first hours of a month it falls back to the previous month).reviews: the newest reviews, comparisons and hands-on articles of the current calendar year (falls back to the previous year in the first hours of January).
PhoneArena has no per-topic feeds, so these three listings are the complete inventory (checked on 2026-09-25). Topic hub pages (for example the Galaxy Z Flip hub) are not articles and are not included.
Sampled response
- Request, 14 Oct 2026
- GET /phonearena/sections
- Items in sections
- 3
- Fields filled in every checked item
- 3
| Field | Filled in, of 3 checked | Values in the sample |
|---|---|---|
| slug | 3 | |
| name | 3 | “News (last two days)” and 2 other values |
| url | 3 | phonearena.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/phonearena/sections" \ -H "x-api-key: $CRAWLORA_API_KEY"
Example JSON response
{
"code": 200,
"data": {
"sections": [
{
"slug": "news",
"name": "News (last two days)",
"url": "https://www.phonearena.com/sitemaps/googlenews.xml"
},
{
"slug": "news-month",
"name": "News (current month)",
"url": "https://www.phonearena.com/sitemaps/news/index.xml"
},
{
"slug": "reviews",
"name": "Reviews (current year)",
"url": "https://www.phonearena.com/sitemaps/reviews/index.xml"
}
]
}
}Request schema
No body schema
Response schema
#/definitions/publicnews.sectionsResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| data | newsplatform.SectionsResponse | No | ||||
| data.sections | array | No | ||||
| data.sections[].name | string | No | ||||
| data.sections[].slug | string | No | ||||
| data.sections[].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/phonearena/sections" \
-H "x-api-key: $CRAWLORA_API_KEY"