/lpse/non_tenders

POST /api/lpse/non_tenders

Price: 5 credits

One non-tender package of an Indonesian LPSE procurement office on SPSE (spse.inaproc.id) by id: the announcement (agency, work unit, procurement category and method, budget sources, budget ceiling and owner's estimate, contract type, locations, plan (RUP) items, qualification requirements and permits), the stage schedule, the participants with their prices, the winners and the contracted winners with contract value.

How to use it

Takes the `id` and `instance` of an lpse/non_tenders/search row, or a package URL alone. Participant tax ids are published masked.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• package_id string required — Non-tender package id or its SPSE page URL (examples: "10650053000", "https://spse.inaproc.id/pu/nontender/10650053000/pengumumanpl"; minLength: 5)
• instance string nullable — LPSE instance code or its legacy host (examples: "pu", "lpse.pu.go.id"; minLength: 2)

Response

• @type string (default: "LpseNonTender")
• id string required
• name string nullable
• labels array (default: [])
• description string nullable
• description_document_name string nullable
• description_document_url string nullable
• created_date string nullable
• stage string nullable
• agency string nullable
• work_unit string nullable
• procurement_category string nullable
• procurement_method string nullable
• is_oap_restricted boolean nullable
• budget_sources array (default: [])
• budget_ceiling number nullable
• estimated_value number nullable
• contract_type string nullable
• locations array (default: [])
• business_qualification string nullable
• technical_weight number nullable
• cost_weight number nullable
• reverse_auction string nullable
• retender_reason string nullable
• cancellation_reason string nullable
• continued_from_id string nullable
• continued_from_name string nullable
• continuation_reason string nullable
• participant_count integer nullable
• plan_items array (default: [])
  • @type string (default: "LpsePlanItem")
  • rup_code string nullable
  • package_name string nullable
  • funding_source string nullable
• qualification_requirements array (default: [])
• qualification_requirements_url string nullable
• permits array (default: [])
  • @type string (default: "LpsePermit")
  • permit_type string nullable
  • requirement string nullable
• business_classifications array (default: [])
  • @type string (default: "LpseBusinessClassification")
  • division string nullable
  • group string nullable
  • description string nullable
  • year string nullable
• schedule array (default: [])
  • @type string (default: "LpseScheduleStage")
  • position integer nullable
  • stage string nullable
  • start_at integer nullable
  • end_at integer nullable
  • change_count integer nullable
• participants array (default: [])
  • @type string (default: "LpseParticipant")
  • position integer nullable
  • name string nullable
  • tax_id_masked string nullable
  • bid_price number nullable
  • corrected_price number nullable
  • negotiated_price number nullable
  • reverse_auction_price number nullable
• winners array (default: [])
  • @type string (default: "LpseWinner")
  • name string nullable
  • address string nullable
  • tax_id_masked string nullable
  • bid_price number nullable
  • corrected_price number nullable
  • negotiated_price number nullable
  • reverse_auction_price number nullable
• contract_winners array (default: [])
  • @type string (default: "LpseContractWinner")
  • name string nullable
  • address string nullable
  • tax_id_masked string nullable
  • contract_value number nullable
  • domestic_content_value number nullable
  • small_business_value number nullable
  • contract_status string nullable
• instance string required
• 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 — No public non-tender package under that id on that instance 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.