/tdb/bankruptcy_summaries/search

POST /api/tdb/bankruptcy_summaries/search

Price: 1 credit

Search Teikoku Databank bankruptcy statistics reports (倒産集計) — monthly, half-year, calendar-year and fiscal-year counts and liabilities of Japanese corporate bankruptcies — by period, publication year and keyword: title, covered period and year, publication date, newest first

How to use it

At most 100 reports per query; narrow by period or year for more. The report text and PDF files come with tdb/bankruptcy_summaries.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of results (min: 1; max: 100)
• period string nullable — Period the report covers (one of: "monthly", "half_year", "calendar_year", "fiscal_year")
• year integer nullable — Publication year (min: 2013; max: 2100)
• keyword string nullable — Words to find in the report (examples: "2024年"; minLength: 1)

Response

• @type string (default: "TdbBankruptcySummary")
• id string required
• url string required
• period string nullable (one of: "monthly", "half_year", "calendar_year", "fiscal_year")
• year integer nullable
• published_date integer nullable
• published_at integer nullable
• created_at integer nullable
• updated_at integer nullable
• text string nullable
• html string nullable
• files array (default: [])
  • @type string (default: "TdbFile")
  • name string nullable
  • url string required
  • file_type string nullable
  • size_bytes integer 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.