The Japan Times API Documentation

First request

Endpoint

GET /japantimes/sections

Cost

1 credit/request

curl "https://api.crawlora.net/api/v1/japantimes/sections" \
  -H "x-api-key: $CRAWLORA_API_KEY"

How to use The Japan Times endpoints

The Japan Times is an English-language Japanese newspaper covering Japan, business, opinion, culture, and sports. A live /japantimes/sections response on 2026-10-14 contained 60 section records; refresh it before scheduling because publisher feeds change. Select from the returned news, business, opinion, culture, and sports section slugs, keeping the original section label with each result. Use canonical HTTPS story URLs for article requests and the numeric-ID /author/ profile form for contributor archives; this is profile lookup rather than byline search. A canonical article route does not establish subscriber access or permission to republish. The publisher's republishing policy requires permission; its link policy permits only limited attributed excerpts. Respect returned public text and access state. Use the endpoint cards for this integration's accepted inputs.

1. Step 1

   Select from the returned desk slugs

   A live /japantimes/sections response on 2026-10-14 contained 60 section records; refresh it before scheduling because publisher feeds change. Select from the returned news, business, opinion, culture, and sports section slugs, keeping the original section label with each result. Use canonical HTTPS story URLs for article requests and the numeric-ID /author/ profile form for contributor archives; this is profile lookup rather than byline search.

2. Step 2

   Keep the republication policy separate from access

   The contributor route is a numeric-ID public profile URL, not a search over arbitrary bylines. Before using extracted text beyond internal monitoring, follow The Japan Times republication policy; a public article response does not grant reuse rights or prove subscription access.

3. Step 3

   Keep the original section label with each result

   The contributor route is a numeric-ID public profile URL, not a search over arbitrary bylines. Before using extracted text beyond internal monitoring, follow The Japan Times republication policy; a public article response does not grant reuse rights or prove subscription access. Pass only a value returned by /japantimes/sections and accepted by /japantimes/headlines; preserve the selected desk with its results.

4. Step 4

   Use canonical HTTPS story URLs

   A canonical article route does not establish subscriber access or permission to republish. The publisher's republishing policy requires permission; its link policy permits only limited attributed excerpts. Respect returned public text and access state. Keep teaser, truncation, premium, or access fields beside the canonical URL so downstream users can see what the publisher actually returned.

5. Step 5

   Look up numeric-ID profile URLs

   Select from the returned news, business, opinion, culture, and sports section slugs, keeping the original section label with each result. Use canonical HTTPS story URLs for article requests and the numeric-ID /author/ profile form for contributor archives; this is profile lookup rather than byline search. A canonical article route does not establish subscriber access or permission to republish. The publisher's republishing policy requires permission; its link policy permits only limited attributed excerpts. Respect returned public text and access state.

Other Media & Streaming APIs