/bdegp/awards

POST /api/bdegp/awards

Price: 1 credit

One contract award from Bangladesh's national e-GP portal by awarded lot and tender ID: ministry, agency and procuring entity, method, funding, project, package, advertisement, award notification, signing and completion dates, exact contract price, supplier with tenderer ID, address and beneficial owners, delivery location, tender counts where published and the authorised officer.

How to use it

Pass `id` and `tender_id` together from one bdegp/awards/search row, or the award URL alone.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Awarded lot id or contract award URL (examples: "2180446", "https://www.eprocure.gov.bd/resources/common/ViewAwardedContracts.jsp?pkgLotId=2180446&tenderid=1336907"; minLength: 1)
• tender_id string nullable — Tender ID the lot belongs to (examples: "1336907"; minLength: 1)

Response

• @type string (default: "BdegpAward")
• id string required
• tender_id string required
• reference string nullable
• ministry string nullable
• agency string nullable
• buyer_name string nullable
• buyer_code string nullable
• buyer_district string nullable
• procurement_nature string nullable
• procurement_method string nullable
• budget_type string nullable
• funding_source string nullable
• development_partner string nullable
• project_code string nullable
• project_name string nullable
• package_number string nullable
• package_name string nullable
• advertised_at integer nullable
• award_notified_date string nullable
• contract_signed_date string nullable
• completion_date string nullable
• proposed_start_date string nullable
• proposed_completion_date string nullable
• contract_number string nullable
• contract_description string nullable
• contract_price number nullable
• contract_currency string nullable
• supplier_name string nullable
• supplier_tenderer_id string nullable
• supplier_address string nullable
• beneficial_owners array (default: [])
  • @type string (default: "BdegpOwner")
  • company_name string nullable
  • name string nullable
  • designation string nullable
  • share number nullable
  • country_name string nullable
• delivery_location string nullable
• tenders_sold_count integer nullable
• tenders_received_count integer nullable
• tenders_responsive_count integer nullable
• has_timely_performance_security boolean nullable
• is_signed_on_time boolean nullable
• authorised_officer_name string nullable
• authorised_officer_designation string 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 — No award for that lot and tender ID pair 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.