/toyokeizai/articles

POST /api/toyokeizai/articles

Price: 20 credits

Get a Toyo Keizai Online article by id or URL: title, description, publication time, author, editor, genre, series, keywords, companies, industries and themes it covers, image, reading time, membership level, page count, the text of every page served to guests and the images in it with their captions

How to use it

A members-only article carries its free part only; is_truncated marks a body cut by the paywall and hidden_characters the length left out.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Toyo Keizai Online article id or URL (examples: "959260", "https://toyokeizai.net/articles/-/959260?page=2")

Response

• @type string (default: "ToyokeizaiArticle")
• id string required
• url string required
• description string nullable
• published_at integer nullable
• author_name string nullable
• author_id string nullable
• editor string nullable
• genre string nullable
• genre_code string nullable
• series string nullable
• column string nullable
• keywords array (default: [])
• companies array (default: [])
• industries array (default: [])
• themes array (default: [])
• image string nullable
• reading_minutes integer nullable
• membership string nullable
• is_members_only boolean nullable
• page_count integer nullable
• pages_read integer nullable
• is_truncated boolean nullable
• hidden_characters integer nullable
• body string nullable
• images array (default: [])
  • @type string (default: "ToyokeizaiArticleImage")
  • image string required
  • caption string nullable

Errors

• 422 — id is not an article id or URL Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No Toyo Keizai Online article under that id Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.