/bdegp/experience

POST /api/bdegp/experience

Price: 1 credit

One work experience certificate from Bangladesh's national e-GP portal by id: certificate number, ministry, organisation and procuring entity, tender and package, nature, method, work category and name, completion status, contract number, value and dates, physical and financial progress with their dates, contractor, joint-venture flag, remarks and the procuring entity's comments.

How to use it

Pass a row's `id` from bdegp/experience/search, not its certificate number.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Work experience certificate id or URL (examples: "259989", "https://www.eprocure.gov.bd/resources/common/VieweCmsDetails.jsp?wcs=completed&Id=259989"; minLength: 1)

Response

• @type string (default: "BdegpExperience")
• id string required
• certificate_number string nullable
• ministry string nullable
• organization string nullable
• buyer_name string nullable
• buyer_officer_name string nullable
• tender_id string nullable
• reference string nullable
• package_name string nullable
• package_number string nullable
• procurement_nature string nullable
• procurement_method string nullable
• work_category string nullable
• work_name string nullable
• work_status string nullable
• tender_published_date string nullable
• tender_type string nullable
• contract_start_date string nullable
• contract_end_date string nullable
• contract_number string nullable
• contract_value number nullable
• physical_progress number nullable
• financial_progress number nullable
• physical_progress_date string nullable
• financial_progress_date string nullable
• supplier_name string nullable
• is_jvca boolean nullable
• remarks string nullable
• buyer_comments 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 work experience certificate under that id 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.