9to5Google API endpoint
Returns the 58 topic guides linked by the current first-party Guides directory and five separately navigable editorial feeds. Use each slug with the headlines endpoint.
/ninetofivegoogle/sectionsReturns the exact 63 accepted headline sections: 58 topics linked from the current first-party Guides directory and five separately linked editorial archive feeds. Every section includes its slug, display name, and RSS URL.
The accepted slugs are: gemini, google-pixel-9-pro-fold, google-pixel-9-pro-xl, google-pixel-9-pro, google-pixel-9, google-pixel-8-pro, google-pixel-8, google-pixel-watch-3, google-pixel-watch, google-pixel-buds-pro-2, google-pixel-buds-pro, google-nest-hub, google-nest-hub-max, google-nest-mini, google-nest-audio, nest-thermostat, nest-cam, google-nest-doorbell, android-17, android-auto, wear-os, samsung, oneplus, oppo, xiaomi, google-chrome, chrome-os, google-tv, android-tv, chromecast, chromecast-with-google-tv, gmail, google-meet, google-chat, google-calendar, google-keep, google-drive, google-docs, youtube, youtube-music, youtube-tv, android, android-14, android-15, android-15-beta, apk-insight, apps-and-updates-2, exclusives, fitbit, google, google-apps, google-assistant, google-home, google-pixel, pixel-11-buyers-guide, google-play, google-search, made-by-google, feature-exclusives, feature-review, feature-newsletter, feature-videos, feature-sponsored-post.
Start from the checked request: GET /ninetofivegoogle/sections. Live check on 2026-10-14: 63 sections returned. Fields present in every checked item: slug, name, url.
Use a returned section value with Get 9to5Google section headlines.
| Field | Filled in, of 63 checked | Values in the sample |
|---|---|---|
| slug | 63 | |
| name | 63 | “Gemini” and 62 other values |
| url | 63 | 9to5google.com |
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| x-api-key (header) | string | Yes | API key required |
curl -X GET "https://api.crawlora.net/api/v1/ninetofivegoogle/sections" \ -H "x-api-key: $CRAWLORA_API_KEY"
{
"code": 200,
"data": {
"sections": [
{
"slug": "gemini",
"name": "Gemini",
"url": "https://9to5google.com/guides/gemini/feed/"
}
]
}
}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 |
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/ninetofivegoogle/sections" \
-H "x-api-key: $CRAWLORA_API_KEY"