/atpress/releases

POST /api/atpress/releases

Price: 1 credit

Get one @Press press release: title, subtitle, publisher, publication and update time, genres, tags, main image, full body as text and HTML, the issuing company's website, address and social links, and the like count.

How to use it

A newscast code from a release URL resolves to the same release. atpress/releases/comments lists readers' comments when is_comment_open is true.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• release string required — Release id, newscast code or URL (examples: "631550", "4902758", "https://www.atpress.ne.jp/news/631550"; minLength: 1)

Response

• @type string (default: "AtpressRelease")
• id string required
• url string required
• subtitle string nullable
• publisher_name string nullable
• company_id string nullable
• published_at integer nullable
• updated_at integer nullable
• is_newscast boolean nullable
• newscast_code string nullable
• category_id string nullable
• genres array (default: [])
  • @type string (default: "AtpressGenreTag")
  • id string required
  • name string nullable
  • alias string nullable
• tags array (default: [])
• image string nullable
• publisher_logo string nullable
• company_website string nullable
• company_logo string nullable
• company_activities string nullable
• company_address string nullable
• company_facebook_url string nullable
• company_x_url string nullable
• company_youtube_url string nullable
• like_count integer nullable
• is_comment_open boolean nullable
• text string nullable
• html string nullable

Errors

• 422 — The request body did not validate 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 release 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.