eproc2.bihar.gov.in APIeproc2.bihar.gov.in ↗
Access active, past, and cancelled tenders from Bihar Government's e-Procurement portal. Filter by department, keyword, and status. 5 endpoints covering 500+ live tenders.
curl -X GET 'https://api.parse.bot/scraper/85caabf7-463f-4ee5-811c-64ff73525248/get_active_tenders' \ -H 'X-API-Key: $PARSE_API_KEY'
Get all currently active/open tenders from Bihar e-Procurement. Returns all tenders at once (typically 500-900+). Supports filtering by department ID and keyword text search.
| Param | Type | Description |
|---|---|---|
| dept_id | string | Department ID to filter tenders (e.g., '731' for Water Resources, '945' for Road Construction). Get IDs from get_departments endpoint. |
| text_filter | string | Keyword to filter tenders by description or reference number (client-side filtering, case-insensitive) |
{
"type": "object",
"fields": {
"type": "string (always 'active')",
"total": "integer - total number of matching tenders",
"tenders": "array of tender objects with tender_id, tender_ref_no, description, bid_start_date, bid_end_date, bid_open_date, status, dept_id, pac_amount, and other fields"
},
"sample": {
"data": {
"type": "active",
"total": 5,
"tenders": [
{
"org_id": 538,
"status": 3,
"dept_id": 731,
"bid_parts": 2,
"tender_id": 130728,
"pac_amount": null,
"cancel_date": null,
"description": "Embankment Repair, repair of Lining work and construction of 5 no's outlet of 300mm dia within 4.96-10.25km of Dharaut Main Canal",
"bid_end_date": "2026-05-09T09:30:00Z",
"publish_date": "2026-05-05T12:33:45Z",
"bid_open_date": "2026-05-11T10:00:00Z",
"cancel_reason": null,
"org_tender_id": 130533,
"tender_ref_no": "01/2026-27/GR-02/ID Jehanabad/WRD",
"bid_start_date": "2026-05-05T12:45:00Z",
"tender_type_id": 101,
"tender_category_id": 101,
"doc_submission_end_date": null,
"procurement_category_id": 1557
}
]
},
"status": "success"
}
}About the eproc2.bihar.gov.in API
This API exposes tender data from the Bihar Government e-Procurement portal (eproc2.bihar.gov.in) across 5 endpoints. The get_active_tenders endpoint alone typically returns 500–900+ live tender records in a single call, each containing fields like tender_ref_no, bid_start_date, bid_end_date, pac_amount, and dept_id. Past, cancelled, and detailed tender views are also available, along with a full department directory for filtering.
Tender Listings by Status
The API covers three tender lifecycle states. get_active_tenders returns all currently open tenders in one response — no pagination needed — and accepts an optional dept_id to scope results to a single department, plus a text_filter for case-insensitive keyword matching against description and reference number fields. get_past_tenders covers closed tenders and uses server-side pagination via page and page_size parameters, returning a has_more flag to drive iteration. get_cancelled_tenders returns cancelled records including cancel_date and cancel_reason; because the full cancelled dataset runs into many thousands of records, using the dept_id filter is strongly recommended.
Tender Detail and Department Directory
get_tender_details accepts a numeric tender_id (obtained from any listing endpoint) and returns fields not present in list views: pac_amount (Probable Amount of Contract), nit (Notice Inviting Tender text), currency, bid_parts, indent_no, and schedule dates. get_departments returns the full directory of participating Bihar government bodies, each with department_id, parent_id, name, code, and hierarchy — the department_id values from this endpoint map directly to dept_id filter parameters across all listing endpoints.
Filtering and Pagination Notes
For active tenders, text_filter is applied client-side after the full dataset is fetched, so all 500–900+ records are retrieved before filtering. For past and cancelled tenders, text_filter and dept_id interact with server-side logic. The tender_id field returned in listing responses is the key to retrieving full detail via get_tender_details — it is a numeric string (e.g., '130728') rather than the human-readable tender_ref_no.
- Monitor all open Bihar government infrastructure tenders filtered by the Road Construction department (
dept_id: '945') to track new bid opportunities. - Build a tender alert system by polling
get_active_tendersand comparingbid_end_dateagainst today's date for upcoming deadlines. - Retrieve
pac_amountandnittext viaget_tender_detailsto populate a contract value analysis dashboard. - Audit cancelled procurement by pulling
get_cancelled_tenderswith a specificdept_idand reviewingcancel_reasonfields for patterns. - Construct a department-to-tender index by combining
get_departmentsoutput with filtered calls toget_active_tendersfor eachdepartment_id. - Page through historical closed tenders using
get_past_tenderswithpageandpage_sizeto build a local archive for trend analysis.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does eproc2.bihar.gov.in have an official developer API?+
What does `get_cancelled_tenders` return, and why is filtering recommended?+
tender_id, tender_ref_no, description, cancel_date, and cancel_reason. The full unfiltered cancelled dataset spans many thousands of records, so passing a dept_id is strongly recommended to limit response size and latency.Does `get_tender_details` return bid document attachments or corrigendum notices?+
get_tender_details covers fields like pac_amount, nit, currency, bid_parts, indent_no, and schedule dates, but does not include attached documents or corrigendum notices. You can fork this API on Parse and revise it to add an endpoint targeting those resources.How does `text_filter` behave differently across endpoints?+
get_active_tenders, filtering is client-side: the full dataset (500–900+ records) is fetched first, then matched case-insensitively against description and tender_ref_no. For get_past_tenders and get_cancelled_tenders, the filter interacts with server-side query logic, so results are scoped before transmission.