/jpportal/jetro/search

POST /api/jpportal/jetro/search

Price: 1 credit

Search the JETRO database of English-language Japanese government procurement notices, national or local, by keyword, notice type, procuring entity, prefecture, product classification and publishing date window. Each row is the notice id, title, publishing date, procuring entity and notice type or location.

How to use it

Rows run newest first. `entity_code`, `area_code` and `classification_code` take the codes JETRO prints beside each name. Pass a row's `id` to jpportal/jetro for the full English notice.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• scope string — National or local government notices (default: "national"; one of: "national", "local")
• keyword string nullable — Words in the notice (examples: "computer"; minLength: 1)
• notice_type string nullable — Kind of national notice (one of: "goods_and_services", "selective_tendering", "construction", "public_offering", "single_tendering", "request_for_materials", "request_for_comments", "future_procurement")
• entity_code string nullable — Procuring entity code (examples: "0010"; minLength: 1; maxLength: 6)
• area_code string nullable — Prefecture code (examples: "13"; pattern: ^\d{2}$)
• classification_code string nullable — Product or service classification code (examples: "0014"; pattern: ^\d{4}$)
• published_from string nullable — Earliest publishing day (format: date; examples: "2026-09-01")
• published_to string nullable — Latest publishing day (format: date; examples: "2026-09-25")
• count integer required — Max number of notices to return (min: 1; max: 1500)

Response

• @type string (default: "JpportalJetroListing")
• id string required
• scope string required (one of: "national", "local")
• published_date string nullable
• entity string nullable
• notice_type string nullable
• location string nullable
• url string required

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.