Docs menu
Phys.org API endpoint
Phys.org sections API
Lists the seven topic feeds in Phys.org's Topics menu and its two additional public Breaking and Editorials feeds. Every returned slug is accepted by physorg-headlines. Search and tag feeds are not included.
GETapiKey1 credit/requestPhys.orgpublicnews.sectionsResponseDoc
Phys.org/physorg/sectionsEndpoint facts
- Method
- GET
- API path
- /physorg/sections
- Auth
- apiKey
- Credits
- 1 credit/request
- Charged on
- Successful 2xx responses only
- Platform
- Phys.org
- Response schema
- #/definitions/publicnews.sectionsResponseDoc
How this endpoint behaves
Query parameters: none.
Returns every verified RSS section slug accepted by physorg-headlines: nanotech-news, physics-news, space-news, earth-news, chemistry-news, biology-news, science-news, breaking, and editorials.
Notable response behavior: section slugs are exact upstream feed path segments. The seven Topics-menu entries are followed by the public Breaking and Editorials feeds. Search, tag, and sort feeds are excluded because the site's robots rules disallow them.
Workflow check
Start from the checked request: GET /physorg/sections. Live check on 2026-10-14: 9 sections returned. Fields present in every checked item: slug, name, url.
Use a returned section value with Get Phys.org section headlines.
Live monitoring
- Monitored request
- GET /physorg/sections
- Checks passed, 7 days to 14 Oct 2026
- 100%
- Median response time
- 0.08 s
Sampled response
- Request, 14 Oct 2026
- GET /physorg/sections
- Items in sections
- 9
- Fields filled in every checked item
- 3
| Field | Filled in, of 9 checked | Values in the sample |
|---|---|---|
| slug | 9 | |
| name | 9 | “Nanotechnology” and 8 other values |
| url | 9 | phys.org |
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/physorg/sections" \ -H "x-api-key: $CRAWLORA_API_KEY"
Illustrative JSON response shape
{
"code": 200,
"data": {
"sections": [
{
"slug": "physics-news",
"name": "Physics"
}
]
},
"msg": "OK"
}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/physorg/sections" \
-H "x-api-key: $CRAWLORA_API_KEY"