Docs menu
Philadelphia Inquirer API endpoint
Philadelphia Inquirer sections API
Lists the 24 Philadelphia Inquirer section slugs accepted by `phillyinquirer-headlines`, such as `news`, `sixers`, `eagles` and `south-jersey`. Each entry has a `slug`, display `name` and `url`. Sub-sections such as `news/philadelphia` are not listed because the `news` section already contains them.
GETapiKey1 credit/requestPhiladelphia Inquirerpublicnews.sectionsResponseDoc
Philadelphia Inquirer/phillyinquirer/sectionsEndpoint facts
- Method
- GET
- API path
- /phillyinquirer/sections
- Auth
- apiKey
- Credits
- 1 credit/request
- Charged on
- Successful 2xx responses only
- Platform
- Philadelphia Inquirer
- Response schema
- #/definitions/publicnews.sectionsResponseDoc
How this endpoint behaves
Returns the public Philadelphia Inquirer section taxonomy accepted by phillyinquirer-headlines. Each entry has a slug, a display name, and the public feed url. The accepted slugs are: arts, business, college-sports, crime, eagles, education, entertainment, flyers, food, health, high-school-sports, life, news, opinion, phillies, politics, real-estate, science, sixers, soccer, south-jersey, sports, transportation, weather.
This is the set of top-level site categories whose public feed returned at least three stories when the list was last verified. Smaller or empty categories (for example cars, consumer, obituaries) and sub-sections such as news/philadelphia are not included: the news feed already contains its sub-sections. Feeds return the most recent stories, from a few to several dozen depending on the section.
Sampled response
- Request, 14 Oct 2026
- GET /phillyinquirer/sections
- Items in sections
- 24
- Fields filled in every checked item
- 3
| Field | Filled in, of 24 checked | Values in the sample |
|---|---|---|
| slug | 24 | |
| name | 24 | “Arts” and 23 other values |
| url | 24 | inquirer.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/phillyinquirer/sections" \ -H "x-api-key: $CRAWLORA_API_KEY"
Example JSON response
{
"code": 200,
"data": {
"sections": [
{
"slug": "sixers",
"name": "Sixers",
"url": "https://www.inquirer.com/arc/outboundfeeds/rss/category/sixers/?outputType=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/phillyinquirer/sections" \
-H "x-api-key: $CRAWLORA_API_KEY"