/ppra/tenders/search

POST /api/ppra/tenders/search

Price: 20 credits

Search federal tenders published on Pakistan's PPRA e-Publish system, open or closed, by keyword, tender number, notice type, procurement category, sector, local or international nature, published or cancelled status, procuring organisation, city, advertisement date range or closing date. Each row carries the tender number, title, reference, sector, ministry, procuring office, city, status, the cancellation reason where the status is cancelled, whether a corrigendum has been issued, advertisement date and closing time.

How to use it

Set `scope` to history for tenders whose bidding has closed, because the default lists only open ones. Pass a row's `id` to ppra/tenders for the description, contacts, bid security and corrigenda.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• scope string — Tenders open for bidding, or closed ones (default: "active"; one of: "active", "history")
• keyword string nullable — Words to search for (examples: "supply"; minLength: 1)
• tender_no string nullable — PPRA tender number (examples: "TS0000014596E"; minLength: 1)
• tender_type string nullable — Notice type (one of: "tender_notice", "prequalification", "request_for_proposal", "expression_of_interest")
• procurement_category string nullable — Procurement category (one of: "goods", "works", "consultancy_services", "non_consultancy_services")
• sector string nullable — Sector (one of: "ammunition", "appliances", "books_journals_manuals", "chemical_items", "civil_goods", "civil_works", "clothing_uniform", "consumable_items", "electrical_items", "equipments", "food_items", "furniture_fixture", "health_medicines", "info_and_comm_tech", "leasing", "petroleum_oil_lubricants", "mechanical_machinery", "mining", "miscellaneous", "printing", "repair_maintenance", "research_development", "services", "stationery", "vehicles", "agricultural_products", "coal", "lng_lpg")
• tender_nature string nullable — Local or international tender (one of: "local", "international")
• status string nullable — Published or cancelled (one of: "published", "cancelled")
• organization string nullable — Organisation name as listed in a row's organization field (examples: "Ministry of Commerce", "Ministry of Finance"; minLength: 1)
• city string nullable — City of the procuring office (examples: "Lahore"; minLength: 1)
• advertised_from string nullable — Earliest advertisement date (format: date)
• advertised_to string nullable — Latest advertisement date (format: date)
• closing_date string nullable — Bid closing date (format: date)
• count integer required — Max number of results (min: 1; max: 2000)

Response

• @type string (default: "PpraTenderSummary")
• id string required
• name string nullable
• reference string nullable
• sector string nullable
• organization string nullable
• buyer_name string nullable
• city string nullable
• country_name string nullable
• status string nullable
• cancellation_reason string nullable
• has_corrigendum boolean (default: false)
• advertised_date string nullable
• closing_at integer 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.