POST /api/gem/bids/results
Price: 20 credits
The published evaluation of one GeM bid or reverse auction: its status, dates and buyer, and every participating seller with the offered item, participation time, MSE and MII preference, technical qualification, offered price and L-rank.
`sellers[].stage` tells a technical-evaluation row from a financial one; a bid still under technical evaluation returns the header with no sellers. A reverse auction ranks the sellers of its parent bid, so pass `parent_id` to see who qualified technically.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)id string required — GeM bid or reverse-auction number (examples: "GEM/2026/B/7943100", "GEM/2026/R/739676"; minLength: 1)@type string (default: "GemBidResult")id string requirednumeric_id string requiredbid_type string nullableparent_id string nullablestatus string nullablequantity integer nullableoffer_validity_days integer nullablestart_at integer nullableend_at integer nullableopening_at integer nullablemin_turnover string nullableexperience_required string nullablecontract_duration string nullableis_project_experience_required boolean nullablebuyer_name string nullablebuyer_address string nullableministry string nullablestate string nullabledepartment string nullableorganisation string nullableoffice string nullablesellers array (default: [])@type string (default: "GemResultSeller")stage string nullableposition integer nullablename string nullableoffered_item string nullableparticipated_at integer nullablepreferences array (default: [])mse_social_category string nullablestatus string nullableprice number nullableprice_basis string nullablerank string nullablenotices array (default: [])url string nullable422 — 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 bid or reverse auction carries that number, or GeM has not published its evaluation yet 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.