/jpportal/tenders/search

POST /api/jpportal/tenders/search

Price: 20 credits

Search Japanese national government procurement cases on the p-portal by procurement name, procuring organisation, case number, notice type, goods/services or public works, prefecture, item classification and publication start and end windows. Each row is the case number, name, organisation, location and its currently published notices (materials and comment requests, procurement notice, award notice) with their ids and publication dates.

How to use it

Rows run in ascending case number, and the source serves at most the first 500 matches of a query, so narrow the publication window to reach recent cases in a busy period. Pass a notice's `notice_id` to jpportal/tenders for the full notice text and documents. WTO award notices carry no case number, so their rows have `id` null. An `org_name` matching no ministry or agency returns no rows.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Words in the procurement name (examples: "重油"; minLength: 1)
• org_name string nullable — Procuring ministry or agency; every organisation whose name contains this text is searched (examples: "国土交通省", "防衛"; minLength: 1)
• procurement_number string nullable — Procurement case number (examples: "0000000000000241194"; minLength: 1)
• published_from string nullable — Earliest publication start day (format: date; examples: "2026-09-01")
• published_to string nullable — Latest publication start day (format: date; examples: "2026-09-25")
• publication_end_from string nullable — Earliest publication end day (format: date; examples: "2026-10-01")
• publication_end_to string nullable — Latest publication end day (format: date; examples: "2026-10-31")
• notice_type array nullable — Notice types; a case matches when it carries any of them (one of: "annual_procurement_plan", "procurement_seminar", "materials_request", "comment_request", "wto_open_tender", "wto_designated_tender", "negotiated_contract", "open_tender", "designated_tender", "proposal_request", "open_counter", "open_counter_small", "wto_award", "award", "negotiated_award"; examples: ["open_tender"])
• category string nullable — Goods and services, or simple public works (one of: "goods_services", "public_works"; examples: "goods_services")
• prefecture array nullable — Prefectures where the case is located (one of: "北海道", "青森県", "岩手県", "宮城県", "秋田県", "山形県", "福島県", "茨城県", "栃木県", "群馬県", "埼玉県", "千葉県", "東京都", "神奈川県", "新潟県", "富山県", "石川県", "福井県", "山梨県", "長野県", "岐阜県", "静岡県", "愛知県", "三重県", "滋賀県", "京都府", "大阪府", "兵庫県", "奈良県", "和歌山県", "鳥取県", "島根県", "岡山県", "広島県", "山口県", "徳島県", "香川県", "愛媛県", "高知県", "福岡県", "佐賀県", "長崎県", "熊本県", "大分県", "宮崎県", "鹿児島県", "沖縄県"; examples: ["東京都","大阪府"])
• item_classification array nullable — Item classification codes (examples: ["027","041"])
• count integer required — Max number of procurement cases to return (min: 1; max: 500)

Response

• @type string (default: "JpportalTenderListing")
• id string nullable
• org_name string nullable
• location string nullable
• notices array (default: [])
  • @type string (default: "JpportalNotice")
  • kind string required
  • notice_id string required
  • published_date 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.