/ppra/evaluations

POST /api/ppra/evaluations

Price: 1 credit

One bid evaluation report from Pakistan's PPRA e-Publish system by evaluation number: tender title and inquiry number, evaluation stage, number of bids, lowest bidder, evaluation fee, procuring organisation and office with contacts, evaluation publication date, the tender's advertisement date and closing time and the evaluated tender number.

How to use it

Pass an evaluation number from ppra/evaluations/search; `tender_id` links back to ppra/tenders.

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 evaluation number or evaluation URL (examples: "EVL00000003768", "https://epms.ppra.gov.pk/public/evaluations/evaluation-details/EVL00000003768"; minLength: 1)

Response

• @type string (default: "PpraEvaluation")
• id string required
• name string nullable
• evaluation_type string nullable
• tender_reference string nullable
• bids_count integer nullable
• lowest_bidder string nullable
• evaluation_fee number 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
• published_date string nullable
• tender_advertised_date string nullable
• tender_closing_at integer nullable
• tender_id 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 evaluation 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.