Discover/Nic API
live

Nic APIetender.up.nic.in ↗

Access active tender listings from the Uttar Pradesh government eProcurement portal. List organisations, fetch tender IDs, titles, dates, and detail URLs.

Endpoint health
verified 2h ago
list_organisations
list_active_tenders
2/2 passing latest checkself-healing
Endpoints
2
Updated
2h ago

What is the Nic API?

The etender.up.nic.in API exposes 2 endpoints to retrieve active tender data from the Uttar Pradesh government eProcurement portal. The list_organisations endpoint returns every organisation currently holding at least one active tender along with its tender count. The list_active_tenders endpoint returns paginated tender rows — including tender ID, reference number, published and closing dates, and a direct detail URL — for any named organisation.

This call costs1 credit / call— charged only on success
Try it

No input parameters required.

→ api.parse.bot/scraper/af510434-d388-4b4d-a1f6-e500f567051c/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/af510434-d388-4b4d-a1f6-e500f567051c/list_organisations' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace etender-up-nic-in-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""Walkthrough: UP eTender SDK — browse organisations and their active tenders."""
from parse_apis.etender_up_nic_in_api import ETenderUP, OrganisationNotFound

client = ETenderUP()

# List organisations with active tenders; cap to first 5.
for org in client.organisations.list(limit=5):
    print(org.name, f"({org.tender_count} active tenders)")

# Pick the first organisation and drill into its tenders.
org = client.organisations.list(limit=1).first()
if org is not None:
    print(f"\nTenders for {org.name}:")
    for tender in org.tenders.list(limit=3):
        print(f"  {tender.tender_id}: {tender.title[:80]}")
        print(f"    closes {tender.closing_date} | ref {tender.reference_no}")
        print(f"    {tender.detail_url}")

# Construct an organisation by name and list its tenders.
try:
    for tender in client.organisation(name="Agra Development Authority").tenders.list(limit=3):
        print(tender.title[:60], "|", tender.published_date)
except OrganisationNotFound:
    print("Organisation not currently listed on the portal.")

print("\nexercised: organisations.list / organisation() / tenders.list")
All endpoints · 2 totalmissing one? ·

Returns the portal's complete 'Tenders by Organisation' directory: every organisation that currently has at least one active tender, with its active tender count, plus the sum across all organisations. One round trip, no pagination (the site lists all organisations on one page). Use organisation_name values from this result as the organisation input of list_active_tenders; the directory changes as tenders open and close.

Input

No input parameters required.

Response
{
  "type": "object",
  "fields": {
    "organisations": "array of {organisation_name, tender_count}; tender_count is the site's active tender count for that organisation",
    "total_tenders": "integer, sum of tender_count over all organisations",
    "total_organisations": "integer, number of organisations listed"
  },
  "sample": {
    "data": {
      "organisations": [
        {
          "tender_count": 6,
          "organisation_name": "Agra Development Authority"
        },
        {
          "tender_count": 11,
          "organisation_name": "Aligarh Development Authority"
        }
      ],
      "total_tenders": 10331,
      "total_organisations": 140
    },
    "status": "success"
  }
}

About the Nic API

What the API Returns

The API surfaces data from the Uttar Pradesh eProcurement portal at etender.up.nic.in. Two endpoints cover the full discovery workflow: finding which organisations have active tenders, then pulling the full tender table for any one of them. All data reflects the portal's current active-tender state.

list_organisations

This endpoint requires no inputs and returns the complete organisation directory in a single response — no pagination needed. Each entry in the organisations array carries organisation_name and tender_count. The response also includes total_tenders (sum across all organisations) and total_organisations (count of listed entities). Use this endpoint first to get the exact organisation name string required by list_active_tenders.

list_active_tenders

Pass the organisation parameter as an exact string from list_organisations (matching is case-insensitive). The endpoint returns a paginated table controlled by page (1-based) and page_size (clamped to a maximum of 1000). Each object in the tenders array includes tender_id, title, reference_no, organisation_name (full chain with || separators when sub-units are present), published_date, closing_date, opening_date, and detail_url. The total_count field gives the organisation's total active tender count before paging; has_more indicates whether a subsequent page exists.

Dates and Identifiers

All date fields (published_date, closing_date, opening_date) are returned in the site's native DD-MM-YYYY HH:MM format. The reference_no field may be blank for some tenders as it is optional on the source portal. detail_url points directly to the individual tender page on etender.up.nic.in.

Reliability & maintenanceVerified

The Nic API is a managed, monitored endpoint for etender.up.nic.in — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when etender.up.nic.in changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.

This isn't an official etender.up.nic.in API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.

Last verified
2h ago
Latest check
2/2 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Monitor newly published government tenders in Uttar Pradesh by polling list_active_tenders for target organisations.
  • Build a tender alert system using closing_date to flag tenders approaching their submission deadline.
  • Aggregate tender_count across all organisations from list_organisations to track eProcurement activity over time.
  • Filter tenders by organisation for procurement intelligence dashboards covering UP state departments.
  • Index detail_url links to build a searchable archive of active UP government procurement opportunities.
  • Cross-reference reference_no values with internal procurement databases to avoid duplicate submissions.
  • Identify which organisations have the highest active tender volume using total_tenders and per-org tender_count.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 req/min

Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does etender.up.nic.in have an official developer API?+
No. The National Informatics Centre (NIC) portal at etender.up.nic.in does not publish a documented public developer API or data feed for programmatic access.
What does list_active_tenders return beyond basic tender metadata?+
Each tender record includes tender_id, title, reference_no, organisation_name (with ||-separated sub-unit chains), published_date, closing_date, opening_date, and detail_url. The total_count field tells you how many active tenders the organisation has in total, and has_more indicates whether more pages exist. Fields like bid documents, corrigenda, or tender financial values are not included in the current response.
Can I retrieve tenders without knowing the exact organisation name?+
The organisation parameter for list_active_tenders must match a name from the list_organisations response (case-insensitive). There is no free-text search or partial-match filtering across organisations currently. Call list_organisations first to enumerate valid names, then pass one to list_active_tenders.
Does the API cover closed or archived tenders, not just active ones?+
Not currently. Both endpoints reflect only tenders the portal classifies as active at the time of the request. Historical or expired tenders are not exposed. You can fork this API on Parse and revise it to add an endpoint targeting the portal's closed or archived tender sections.
How should I handle the `reference_no` field being blank for some tenders?+
The reference_no field is optional on the UP eProcurement portal, so some tenders are published without one. Treat it as a nullable string in your data model. Use tender_id as the stable unique identifier for deduplication and lookups.
Page content last updated . Spec covers 2 endpoints from etender.up.nic.in.
Related APIs in Government PublicSee all →
tenders.gov.in API
Search and monitor current government tenders from India's Central Public Procurement Portal and GePNIC systems, filtering by organizations and accessing detailed tender information. Stay updated on the latest procurement opportunities and bids from Indian government agencies in one centralized location.
eprocurement.gov API
Monitor India's public procurement opportunities by accessing active tenders, bids closing today, global tenders, high-value contracts, and cancelled tenders from the Central Public Procurement Portal. Search tender details, browse participating organizations, and track real-time procurement statistics to stay informed on government contracting opportunities.
eprocure.gov.in API
Access data from eprocure.gov.in.
etenders.gov.za API
Access data from etenders.gov.za.
mahatenders.gov.in API
Access Maharashtra government tenders from mahatenders.gov.in, browsing them by closing date or by organization with full tender details and pagination support. Find and review procurement opportunities across different government departments in one place.
eproc2.bihar.gov.in API
Access live tender listings from the Bihar Government e-Procurement portal to search and filter government contracts by department, status, and keywords. Get detailed tender information including specifications and deadlines, plus browse the complete directory of participating government departments.
bdtender.com API
Search and browse tender listings from Bangladesh's largest tender portal, discovering opportunities by category, organization, and location while accessing real-time tender data and site statistics. Get detailed information on individual tenders, view live postings, and see what was published today to stay updated on the latest bidding opportunities.
tenders.etimad.sa API
Browse and search all public Saudi government tenders from the Etimad platform with detailed information including tender specifications and awarding results. Stay updated on procurement opportunities by accessing tender details and award outcomes in one centralized location.