Docs menu
The Japan Times API endpoint
The Japan Times author profile API
Returns a The Japan Times author's name and the article cards linked from their profile page. `url` is required and must be a canonical HTTPS profile link in the form `/author/<numeric-id>/<slug>/`. Each article has a title, URL, summary, author, image, `type` and publication time. Paginated `/page/<n>/` URLs are not followed.
GETapiKey2 credits/requestThe Japan Timespublicnews.japantimesAuthorResponseDoc
The Japan Times/japantimes/authorEndpoint facts
- Method
- GET
- API path
- /japantimes/author
- Auth
- apiKey
- Credits
- 2 credits/request
- Charged on
- Successful 2xx responses only
- Platform
- The Japan Times
- Response schema
- #/definitions/publicnews.japantimesAuthorResponseDoc
How this endpoint behaves
Query parameter: url must be a canonical HTTPS profile URL in the publisher's /author/<numeric-id>/<slug>/ format. Returns public author metadata and linked article cards from the profile page. Paginated /page/<n>/ URLs are not supported.
Workflow check
Start from the checked request: GET /japantimes/author?url=https%3A%2F%2Fwww.japantimes.co.jp%2Fauthor%2F162%2Fkanako-takahara%2F. Live check on 2026-10-14: 30 articles returned. Fields present in every checked item: title, url.
Return to section story discovery with Get The Japan Times section headlines.
Live monitoring
- Monitored request
- GET /japantimes/author?url=https%3A%2F%2Fwww.japantimes.co.jp%2Fauthor%2F162%2Fkanako-takahara%2F
- Checks passed, 7 days to 14 Oct 2026
- 100%
- Median response time
- 3.83 s
Sampled response
- Request, 14 Oct 2026
- GET /japantimes/author?url=https%3A%2F%2Fwww.japantimes.co.jp%2Fauthor%2F162%2Fkanako-takahara%2F
- Items in articles
- 30
- Fields filled in every checked item
- 2
| Field | Filled in, of 30 checked | Values in the sample |
|---|---|---|
| title | 30 | median 70 characters |
| url | 30 | japantimes.co.jp |
Request parameters
| Parameter | Type | Required | Default | Description | Example |
|---|---|---|---|---|---|
| url | string | Yes | Canonical HTTPS /author/<numeric-id>/<slug>/ profile URL | https://www.japantimes.co.jp/author/162/kanako-takahara/ | |
| x-api-key (header) | string | Yes | API key required |
cURL example
curl -X GET "https://api.crawlora.net/api/v1/japantimes/author?url=https%3A%2F%2Fwww.japantimes.co.jp%2Fauthor%2F162%2Fkanako-takahara%2F" \ -H "x-api-key: $CRAWLORA_API_KEY"
Illustrative JSON response shape
{
"code": 200,
"data": {
"name": "Example Author",
"url": "https://www.japantimes.co.jp/author/123/example-author/",
"articles": [
{
"title": "Example headline",
"url": "https://www.japantimes.co.jp/news/2026/09/29/japan/example-story/"
}
]
}
}Request schema
No body schema
Response schema
#/definitions/publicnews.japantimesAuthorResponseDoc
| Field | Type | Required | Enum | Bounds | Example | Description |
|---|---|---|---|---|---|---|
| data | japantimes.AuthorResponse | No | ||||
| data.articles | array | No | HeadlineItem record, 7 fields: author, image_url, published_at, summary, title, type, url. Described under The Japan Times top stories API. | |||
| data.name | 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/author?url=https%3A%2F%2Fwww.japantimes.co.jp%2Fauthor%2F162%2Fkanako-takahara%2F" \
-H "x-api-key: $CRAWLORA_API_KEY"