/gem/bids/search

POST /api/gem/bids/search

Price: 1 credit

Search GeM bids and reverse auctions by keyword or bid number, lifecycle status, evaluation stage, bid type, high-value flag and end-date window. Each result carries the buyer ministry and department, item category, quantity, start and end times, evaluation status, award schedules and the bid document link.

How to use it

Pass a full bid number as `keyword` to find one bid; `exact_match` narrows a keyword to the phrase. `status: closed` holds bids and reverse auctions past their end date, and `stage` narrows those to how far evaluation went. Call gem/bids for the bid document fields and gem/bids/results for the sellers and prices once `evaluation_status` has moved past Not Evaluated.

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 or a bid number to search for (examples: "laptop", "GEM/2026/B/7943100"; minLength: 1)
• exact_match boolean — Match the keyword as an exact phrase (default: false)
• status string — Lifecycle segment of the bids (default: "all"; one of: "all", "ongoing", "closed", "cancelled")
• stage string nullable — Evaluation stage reached by a closed bid or reverse auction (one of: "technical_evaluation", "financial_evaluation", "awarded")
• bid_type string nullable — Kind of bid (one of: "product", "service", "bid_to_ra", "custom", "boq", "rate_contract", "global_tender", "limited_tender", "single_tender")
• high_value boolean — Only high-value bids (default: false)
• end_date_from string nullable — Earliest bid end date (format: date)
• end_date_to string nullable — Latest bid end date (format: date)
• sort string — Order of the results (default: "start_date_desc"; one of: "start_date_desc", "start_date_asc", "end_date_desc", "end_date_asc")
• count integer required — Max number of results (min: 1; max: 1000)

Response

• @type string (default: "GemBid")
• id string required
• numeric_id string required
• bid_type string nullable
• parent_id string nullable
• parent_numeric_id string nullable
• category string nullable
• category_id string nullable
• boq_title string nullable
• is_boq boolean nullable
• is_new_boq boolean nullable
• quantity integer nullable
• ministry string nullable
• department string nullable
• created_by string nullable
• start_at integer nullable
• end_at integer nullable
• is_cancelled boolean nullable
• status_code string nullable
• evaluation_status string nullable
• ra_status_code string nullable
• ra_evaluation_status string nullable
• evaluation_type_code string nullable
• type_code string nullable
• bid_to_ra_code string nullable
• ra_to_bid_code string nullable
• bunch_code string nullable
• is_custom_item boolean nullable
• is_high_value boolean nullable
• is_global_tender boolean nullable
• is_rate_contract boolean nullable
• is_single_packet boolean nullable
• schedules array (default: [])
  • @type string (default: "GemBidSchedule")
  • id string nullable
  • status_code string nullable
  • is_awarded boolean nullable
• parent_schedules array (default: [])
  • @type string (default: "GemBidSchedule")
  • id string nullable
  • status_code string nullable
  • is_awarded boolean nullable
• document_url string nullable

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.