POST /api/bdegp/tenders
Price: 5 credits
One tender notice from Bangladesh's national e-GP portal by tender ID: organisation chain and procuring entity, notice type, method, budget and funding source, project, package, categories, every key date, eligibility and description, document price and fees, validity dates, lots or service phases with security amounts, framework offices, amendments with their field changes and the inviting official.
Pass a tender ID from bdegp/tenders/search, or a `tender_id` from bdegp/awards/search or bdegp/experience/search for request-for-quotation, limited-tendering and direct-procurement tenders, which the tender search does not list. Any status is accepted, cancelled and archived included. Limited-tendering and direct-procurement tenders return the notice fields without status, lots, service phases, framework offices, amendments or the official's address and contacts.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)id string required — Tender ID or tender notice URL (examples: "1317342", "https://www.eprocure.gov.bd/resources/common/ViewTender.jsp?id=1317342&h=t"; minLength: 1)@type string (default: "BdegpTender")id string requiredapp_id string nullablereference string nullablereoi_id string nullableretendered_id string nullablestatus string nullableevent_type string nullableinvitation_for string nullableselection_for string nullableministry string nullabledivision string nullableorganization string nullablebuyer_name string nullablebuyer_code string nullablebuyer_district string nullableprocurement_nature string nullableprocurement_type string nullableprocurement_method string nullablecontract_type string nullablebudget_type string nullablefunding_source string nullabledevelopment_partner string nullableproject_code string nullableproject_name string nullablepackage string nullablecategories array (default: [])published_at integer nullabledocument_deadline_at integer nullablepre_tender_meeting_start_at integer nullablepre_tender_meeting_end_at integer nullableclosing_at integer nullableopening_at integer nullablesecurity_deadline_at integer nullableeligibility string nullabledescription string nullableexperience_requirements string nullableother_details string nullableforeign_association string nullableevaluation_type string nullabledocument_availability string nullabledocument_fees string nullabledocument_price number nullabledocument_price_usd number nullablesecurity_amount number nullablepayment_mode string nullablepassing_points number nullabletechnical_weight number nullablefinancial_weight number nullablesecurity_valid_until_date string nullabletender_valid_until_date string nullableofficial object nullable@type string (default: "BdegpOfficial")name string nullabledesignation string nullableaddress string nullablecity string nullablethana string nullabledistrict string nullablecountry_name string nullablephone string nullablefax string nullableemail string nullablelots array (default: [])@type string (default: "BdegpLot")number string nullablename string nullablelocation string nullablesecurity_amount number nullablesecurity_amount_usd number nullablestart_date string nullablecompletion_date string nullableservice_phases array (default: [])@type string (default: "BdegpServicePhase")reference string nullablename string nullablelocation string nullablestart_date string nullablecompletion_date string nullableframework_offices array (default: [])@type string (default: "BdegpFrameworkOffice")office_name string nullableofficer_name string nullabledesignation string nullableis_lead boolean nullableamendments array (default: [])@type string (default: "BdegpAmendment")number integer nullabletext string nullablechanges array (default: [])@type string (default: "BdegpChange")field string nullableold_value string nullablenew_value string nullabledocuments_url string nullablecurrency string (default: "BDT")url string required422 — 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 notice is available 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.