/tdnet/disclosures/search

POST /api/tdnet/disclosures/search

Price: 10 credits

List timely disclosures filed on TDnet by Japanese listed companies, newest first, optionally narrowed by a company code, company name or title words and by a day range: disclosure time, company code and name, title, previous title of a corrected filing, PDF and XBRL links, listing exchanges and the update trail

How to use it

Without keyword it lists every filing of the last ~40 days; with keyword it searches the last 31 days. Several keyword words must all match.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Company code, company name or words of the disclosure title (examples: "7203", "トヨタ", "決算短信"; minLength: 1; maxLength: 50)
• date_from integer nullable — Earliest disclosure day, unix seconds; day-granular, the UTC day of the value counts (examples: 1788393600)
• date_to integer nullable — Latest disclosure day, unix seconds; day-granular, the whole UTC day of the value counts (examples: 1790985600)
• count integer required — Max number of results (min: 1; max: 6000)

Response

• @type string (default: "TdnetDisclosure")
• id string required
• published_at integer required
• code string required
• local_code string required
• company_name string required
• previous_title string nullable
• pdf_url string required
• xbrl_url string nullable
• exchanges array (default: [])
• update_history 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 — The entity was not found, or a precondition failed 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.