/lpse/tenders/search

POST /api/lpse/tenders/search

Price: 5 credits

List the tenders of one Indonesian LPSE procurement office on SPSE (spse.inaproc.id) for a budget year: package id, name, agency, current stage, abbreviated estimated value, qualification, selection and evaluation method, procurement category, budget years, contract value once signed, and re-tender, consolidation and Papua-only flags.

How to use it

`instance` is the office code from the SPSE address (spse.inaproc.id/pu → `pu`) or the office's old lpse.*.go.id host. Pass `id` with the same `instance` to lpse/tenders for the announcement, schedule, bidders and winners.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• instance string required — LPSE instance code or its legacy host (examples: "pu", "jakarta", "lpse.jatimprov.go.id"; minLength: 2)
• year integer nullable — Budget year of the listing; the instance's current listing year when omitted (min: 2007; max: 2100)
• count integer required — Max number of tenders to return (min: 1; max: 10000)
• offset integer — How many tenders of the listing to skip before the first returned row (default: 0; min: 0)

Response

• @type string (default: "LpseTenderSummary")
• id string required
• name string nullable
• labels array (default: [])
• agency string nullable
• stage string nullable
• estimated_value_label string nullable
• selection_method string nullable
• procurement_category string nullable
• budget_years array (default: [])
• spse_version integer nullable
• contract_value number nullable
• is_consolidated boolean nullable
• is_oap_restricted boolean nullable
• instance string required
• year integer required
• url string required
• qualification_method string nullable
• evaluation_method string nullable
• is_re_evaluation boolean nullable
• is_re_bid boolean 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.