/ppra/tenders

POST /api/ppra/tenders

Price: 1 credit

One federal tender from Pakistan's PPRA e-Publish system by tender number: title, reference, notice type, category, procedure, sector, nature, description, note and remarks, procuring organisation and office with contacts, advertisement date, closing and opening times, bid security and validity, method, workflow, closed flag, cancellation reason and the corrigenda with their dates.

How to use it

Pass a tender number from ppra/tenders/search; open, closed and cancelled tenders all resolve.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — PPRA tender number or tender URL (examples: "TS0000014596E", "https://epms.ppra.gov.pk/public/tenders/tender-details/TS0000014596E"; minLength: 1)

Response

• @type string (default: "PpraTender")
• id string required
• name string nullable
• reference string nullable
• tender_type string nullable
• procurement_category string nullable
• procurement_procedure string nullable
• sector string nullable
• tender_nature string nullable
• description string nullable
• note string nullable
• remarks string nullable
• organization string nullable
• buyer_name string nullable
• buyer_address string nullable
• city string nullable
• contact_name string nullable
• contact_email string nullable
• contact_phone string nullable
• advertised_date string nullable
• closing_at integer nullable
• opening_time string nullable
• bid_security number nullable
• bid_validity string nullable
• procurement_method string nullable
• workflow_type string nullable
• is_closed boolean (default: false)
• cancellation_reason string nullable
• cancellation_justification string nullable
• corrigenda array (default: [])
  • @type string (default: "PpraCorrigendum")
  • number integer nullable
  • issued_at integer nullable
  • closing_date string nullable
  • remarks string nullable
• currency string (default: "PKR")
• 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 tender under that number 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.