Docs menu
Phys.org API endpoint
Phys.org article API
Returns public Phys.org article metadata and readable body paragraphs from a canonical dated news URL. The service tries proxied HTTP first and uses the production browser fleet when the article edge challenges HTTP. Billing is 2 credits for an HTTP-profile success and 10 credits when browser rendering is required. No author-profile route was verified.
GETapiKey2 credits HTTP · 10 with browser renderingPhys.orgpublicnews.articleResponseDoc
Phys.org/physorg/articleEndpoint facts
- Method
- GET
- API path
- /physorg/article
- Auth
- apiKey
- Credits
- 2 credits HTTP · 10 with browser rendering
- Charged on
- Successful 2xx responses only
- Platform
- Phys.org
- Execution
- Managed browser rendering where the target needs it
- Response schema
- #/definitions/publicnews.articleResponseDoc
How this endpoint behaves
Query parameter: required url, a canonical https://phys.org/news/YYYY-MM-<slug>.html article URL.
Notable response behavior: returns public article metadata and readable body paragraphs. Billing is 2 credits, or 10 credits for articles that need heavier processing. The observed byline does not link to an author profile, so this family has no author endpoint.
Workflow check
Start from the checked request: GET /physorg/article?url=https%3A%2F%2Fphys.org%2Fnews%2F2026-09-espionage-boosted-east-germany-economic.html. Live check on 2026-10-14: one record. Fields present in every checked record: url, title, description, published_at, updated_at, section, authors, image_url.
Return to section story discovery with Get Phys.org section headlines.
Live monitoring
- Monitored request
- GET /physorg/article?url=https%3A%2F%2Fphys.org%2Fnews%2F2026-09-espionage-boosted-east-germany-economic.html
- Checks passed, 7 days to 14 Oct 2026
- 100%
- Median response time
- 14.44 s
Sampled response
- Request, 14 Oct 2026
- GET /physorg/article?url=https%3A%2F%2Fphys.org%2Fnews%2F2026-09-espionage-boosted-east-germany-economic.html
- Fields returned with a value
- 9
| Field | In the sample | Value in the sample |
|---|---|---|
| url | Has a value | phys.org |
| title | Has a value | 56 characters |
| description | Has a value | 274 characters |
| published_at | Has a value | 2026-09-28 |
| updated_at | Has a value | 2026-09-28 |
| section | Has a value | “Economics & Business” |
| authors | Has a value | 1 entry |
| image_url | Has a value | scx2.b-cdn.net |
| paragraphs | Has a value | 13 entries |
Request parameters
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| url | string | Yes | Canonical Phys.org article URL | https://phys.org/news/2026-09-espionage-boosted-east-germany-economic.html | |
| x-api-key (header) | string | Yes | API key required |
cURL example
curl -X GET "https://api.crawlora.net/api/v1/physorg/article?url=https%3A%2F%2Fphys.org%2Fnews%2F2026-09-espionage-boosted-east-germany-economic.html" \ -H "x-api-key: $CRAWLORA_API_KEY"
Illustrative JSON response shape
{
"code": 200,
"data": {
"url": "https://phys.org/news/2026-09-example-story.html",
"title": "A Phys.org science story",
"paragraphs": [
"A representative public article paragraph."
]
},
"msg": "OK"
}Request schema
No body schema
Response schema
#/definitions/publicnews.articleResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| data | newsplatform.ArticleResponse | No | ||||
| data.authors | array | No | ||||
| data.description | string | No | ||||
| data.image_url | string | No | ||||
| data.paragraphs | array | No | ||||
| data.paywalled | boolean | No | Paywalled is true when the publisher serves only a teaser of this article to anonymous readers, so Paragraphs is a partial body rather than the full text. It is omitted when the full public body was returned. | |||
| data.published_at | string | No | ||||
| data.section | string | No | ||||
| data.title | string | No | ||||
| data.updated_at | string | No | ||||
| data.url | string | No |
Failure responses
| Status | Description | Schema |
|---|---|---|
| 400 | Bad Request | #/definitions/app.Response |
| 404 | Not Found | #/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/physorg/article?url=https%3A%2F%2Fphys.org%2Fnews%2F2026-09-espionage-boosted-east-germany-economic.html" \
-H "x-api-key: $CRAWLORA_API_KEY"