/bdegp/experience/search

POST /api/bdegp/experience/search

Price: 5 credits

Search work experience certificates issued on Bangladesh's national e-GP portal by source, work status, procurement nature, type and method, tender ID, certificate number, contractor name or tenderer ID, organisation, procuring entity office, contract start and end date ranges, or keyword. Each row carries the certificate number, organisation chain, tender, work, contractor, contract value, dates and status.

How to use it

Pass a row's `supplier_tenderer_id` back as a filter to list one contractor's certificates. Pass a row's `id` to bdegp/experience for progress, contract number and the procuring entity's comments.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string nullable — Words to search for (examples: "auditorium"; minLength: 1)
• source string — Where the contract was run (default: "all"; one of: "all", "e_tenders", "e_cms", "manual")
• work_status string — Work completion status (default: "all"; one of: "all", "completed", "ongoing")
• procurement_nature string nullable — Procurement nature (one of: "goods", "works", "services", "physical_services")
• procurement_type string nullable — National (NCT) or international (ICT) competitive tendering (one of: "nct", "ict")
• procurement_method string nullable — Procurement method (one of: "rfq", "rfqu", "rfql", "otm", "ltm", "tstm", "dpm", "ostetm", "qcbs", "dc", "ic", "sfb", "lcs", "cso", "sss"; examples: "otm", "ltm")
• tender_id string nullable — Tender ID (examples: "783751"; minLength: 1; pattern: ^\d+$)
• certificate_number string nullable — Work experience certificate number (examples: "RHDC/22-23/900/230/e-GP/20260923/783751/00259989"; minLength: 1)
• certificate_match string — How certificate_number is matched (default: "contains"; one of: "contains", "equals")
• supplier_name string nullable — Name of the contractor the work was awarded to (examples: "Parama"; minLength: 1)
• supplier_match string — How supplier_name is matched (default: "contains"; one of: "contains", "equals")
• supplier_tenderer_id string nullable — Contractor's tenderer ID (examples: "1107531"; minLength: 1; pattern: ^\d+$)
• department_id string nullable — Organisation id (examples: "7"; minLength: 1; pattern: ^\d+$)
• office_id string nullable — Procuring entity office id (examples: "2160"; minLength: 1; pattern: ^\d+$)
• contract_start_from string nullable — Earliest contract start date (format: date)
• contract_start_to string nullable — Latest contract start date (format: date)
• contract_end_from string nullable — Earliest contract end date (format: date)
• contract_end_to string nullable — Latest contract end date (format: date)
• count integer required — Max number of results (min: 1; max: 1000)

Response

• @type string (default: "BdegpExperienceSummary")
• id string required
• certificate_number string nullable
• ministry string nullable
• organization string nullable
• buyer_name string nullable
• procurement_nature string nullable
• procurement_type string nullable
• procurement_method string nullable
• tender_id string nullable
• reference string nullable
• work_name string nullable
• tender_published_date string nullable
• supplier_name string nullable
• supplier_tenderer_id string nullable
• contract_value number nullable
• contract_start_date string nullable
• contract_end_date string nullable
• work_status 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 — 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.