Docs menu
The Japan Times API endpoint
The Japan Times article API
Returns public article metadata. If the page marks its body as blurred for anonymous visitors, paywalled is true and hidden subscriber text is omitted.
GETapiKey2 credits/requestThe Japan Timespublicnews.articleResponseDoc
The Japan Times/japantimes/articleEndpoint facts
- Method
- GET
- API path
- /japantimes/article
- Auth
- apiKey
- Credits
- 2 credits/request
- Charged on
- Successful 2xx responses only
- Platform
- The Japan Times
- Response schema
- #/definitions/publicnews.articleResponseDoc
How this endpoint behaves
Query parameter: url must be a canonical HTTPS japantimes.co.jp editorial article URL. The response includes available public metadata. If the publisher marks the body as blurred/paywalled for anonymous visitors, paywalled is true and paragraphs is empty; hidden subscriber text is not returned.
Workflow check
Start from the checked request: GET /japantimes/article?url=https%3A%2F%2Fwww.japantimes.co.jp%2Fnews%2F2026%2F09%2F28%2Fjapan%2Fexplainer%2Fetc-explainer%2F. 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. Observed field variation: paragraphs was empty in this check.
For a known public contributor profile, continue with Get a The Japan Times author profile.
Live monitoring
- Monitored request
- GET /japantimes/article?url=https%3A%2F%2Fwww.japantimes.co.jp%2Fnews%2F2026%2F09%2F28%2Fjapan%2Fexplainer%2Fetc-explainer%2F
- Checks passed, 7 days to 14 Oct 2026
- 99.7%
- Median response time
- 4.33 s
Sampled response
- Request, 14 Oct 2026
- GET /japantimes/article?url=https%3A%2F%2Fwww.japantimes.co.jp%2Fnews%2F2026%2F09%2F28%2Fjapan%2Fexplainer%2Fetc-explainer%2F
- Fields returned with a value
- 9
- Fields returned empty
- 1
| Field | In the sample | Value in the sample |
|---|---|---|
| url | Has a value | japantimes.co.jp |
| title | Has a value | 51 characters |
| description | Has a value | 127 characters |
| published_at | Has a value | 2026-09-27 |
| updated_at | Has a value | 2026-09-28 |
| section | Has a value | “JAPAN” |
| authors | Has a value | 1 entry |
| image_url | Has a value | japantimes.co.jp |
| paywalled | Has a value | true |
| paragraphs | Empty |
Request parameters
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| url | string | Yes | Canonical HTTPS The Japan Times article URL | https://www.japantimes.co.jp/news/2026/09/28/japan/explainer/etc-explainer/ | |
| x-api-key (header) | string | Yes | API key required |
cURL example
curl -X GET "https://api.crawlora.net/api/v1/japantimes/article?url=https%3A%2F%2Fwww.japantimes.co.jp%2Fnews%2F2026%2F09%2F28%2Fjapan%2Fexplainer%2Fetc-explainer%2F" \ -H "x-api-key: $CRAWLORA_API_KEY"
Illustrative JSON response shape
{
"code": 200,
"data": {
"url": "https://www.japantimes.co.jp/news/2026/09/28/japan/explainer/example/",
"title": "Example article",
"published_at": "2026-09-27T17:47:42+09:00",
"section": "JAPAN",
"authors": [
"Example Author"
],
"paywalled": true,
"paragraphs": []
}
}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/japantimes/article?url=https%3A%2F%2Fwww.japantimes.co.jp%2Fnews%2F2026%2F09%2F28%2Fjapan%2Fexplainer%2Fetc-explainer%2F" \
-H "x-api-key: $CRAWLORA_API_KEY"