/gem/bids/search/advanced

POST /api/gem/bids/search/advanced

Price: 1 credit

Search ongoing GeM bids by buyer — ministry or state, then organisation and department — by delivery state and city, or by bill-of-quantities title, optionally within a bid end-date window.

How to use it

Names are matched against GeM's own lists without regard to case, and an unknown name is rejected with the closest listed names, so pass one of those instead. Only one criterion group is accepted per call, and only ongoing bids are returned, so use gem/bids/search for keywords, closed or cancelled bids.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• ministry string nullable — Buyer ministry (examples: "Ministry of Railways"; minLength: 1)
• buyer_state string nullable — Buyer state (examples: "MAHARASHTRA"; minLength: 1)
• organisation string nullable — Buyer organisation (examples: "Central Railway"; minLength: 1)
• department string nullable — Buyer department (examples: "Indian Railways"; minLength: 1)
• consignee_state string nullable — State of the delivery location (examples: "MAHARASHTRA"; minLength: 1)
• consignee_city string nullable — City of the delivery location (examples: "PUNE"; minLength: 1)
• boq_title string nullable — Bill-of-quantities title (examples: "Catheter Foleys"; minLength: 1)
• high_value boolean — Only high-value bids, with boq_title (default: false)
• end_date_from string nullable — Earliest bid end date (format: date)
• end_date_to string nullable — Latest bid end date (format: date)
• 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.