Docs menu
IndieWire API endpoint
IndieWire sections API
Lists IndieWire's 32 editorial categories accepted by `indiewire-headlines`, such as `analysis`, `box-office`, `festivals`, `interviews`, `obituary` and `trailers`. Each entry has a `slug`, display `name` and the category feed `url`. Categories nest under the roots `news`, `features`, `awards` and `criticism`.
GETapiKey1 credit/requestIndieWirepublicnews.sectionsResponseDoc
IndieWire/indiewire/sectionsEndpoint facts
- Method
- GET
- API path
- /indiewire/sections
- Auth
- apiKey
- Credits
- 1 credit/request
- Charged on
- Successful 2xx responses only
- Platform
- IndieWire
- Response schema
- #/definitions/publicnews.sectionsResponseDoc
How this endpoint behaves
Returns IndieWire's complete public section inventory (32 editorial categories as of 2026-09-24), the value space accepted by /api/v1/indiewire/headlines. Categories nest under four roots (news, features, awards, criticism); a section's feed url uses the parent path. The site's genre taxonomy is excluded.
Each section includes a stable slug, display name, and the public upstream RSS feed url for that section.
Allowed section slugs: analysis, animation, awards, awards-premium, best-of, box-office, brand-content, breaking-news, business, commentary, consider-this, craft, criticism, culture, events, features, festivals, film, general, general-news, industry, interviews, movies, news, obituary, podcast, predictions, results, shop, shows, special-projects, trailers.
Sampled response
- Request, 14 Oct 2026
- GET /indiewire/sections
- Items in sections
- 32
- Fields filled in every checked item
- 3
| Field | Filled in, of 32 checked | Values in the sample |
|---|---|---|
| slug | 32 | |
| name | 32 | “Analysis” and 31 other values |
| url | 32 | indiewire.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/indiewire/sections" \ -H "x-api-key: $CRAWLORA_API_KEY"
Example JSON response
{
"code": 200,
"data": {
"sections": [
{
"slug": "analysis",
"name": "Analysis",
"url": "https://www.indiewire.com/c/news/analysis/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 |
Code examples
Use environment variables for secrets and keep Crawlora API keys server-side.
curl -X GET "https://api.crawlora.net/api/v1/indiewire/sections" \
-H "x-api-key: $CRAWLORA_API_KEY"