Docs menu
Android Authority API endpoint
Android Authority sections API
Lists the 44 Android Authority sections that `androidauthority-headlines` accepts: the content-type hubs (`news`, `reviews`, `best`, `how-to`, `features`, `deals`, `authority-insights`), the top-level topic hubs and their sub-hubs. Each has a `slug`, display `name` and page `url`. Tag archives are not sections.
GETapiKey1 credit/requestAndroid Authoritypublicnews.sectionsResponseDoc
Android Authority/androidauthority/sectionsEndpoint facts
- Method
- GET
- API path
- /androidauthority/sections
- Auth
- apiKey
- Credits
- 1 credit/request
- Charged on
- Successful 2xx responses only
- Platform
- Android Authority
- Execution
- Managed browser rendering where the target needs it
- Response schema
- #/definitions/publicnews.sectionsResponseDoc
How this endpoint behaves
Returns the complete public section inventory accepted by /api/v1/androidauthority/headlines (44 hub pages, each verified live 2026-09-25): news, reviews, best, how-to, features, deals, authority-insights, audio, computers-pc, gaming, technology, mobile, smart-home, streaming-entertainment, wearables, earbuds-headphones, chromebook, mac, pc-windows, emulation, handhelds, mobile-games, nintendo, playstation, xbox, smart-devices, smart-speakers, virtual-assistants, streaming-hardware, ai, mobility, privacy-security, vr-ar, fitness-trackers, smartwatches, android-apps, android-os, android-phones, android-tablets, carriers-plans, ios-apps, iphone-ipad, accessories, mobile-technology.
They are the content-type hubs (news, reviews, best, how-to, features, deals, authority-insights), the top-level topic hubs from the site's own navigation, and the topic sub-hubs listed under them. Each section includes a stable slug, display name, and public upstream url. Tag archives (/tag/<slug>/) are not sections.
Sampled response
- Request, 14 Oct 2026
- GET /androidauthority/sections
- Items in sections
- 44
- Fields filled in every checked item
- 3
| Field | Filled in, of 44 checked | Values in the sample |
|---|---|---|
| slug | 44 | |
| name | 44 | “News” and 43 other values |
| url | 44 | androidauthority.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/androidauthority/sections" \ -H "x-api-key: $CRAWLORA_API_KEY"
Example JSON response
{
"code": 200,
"data": {
"sections": [
{
"slug": "news",
"name": "News",
"url": "https://www.androidauthority.com/news/"
},
{
"slug": "reviews",
"name": "Reviews",
"url": "https://www.androidauthority.com/reviews/"
}
]
}
}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 |
Code examples
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/androidauthority/sections" \
-H "x-api-key: $CRAWLORA_API_KEY"