India Government Data API
Pricing
$3.00 / 1,000 data records
India Government Data API
Search India business, procurement, health, legal, and public-data sources in one run. Get normalized results fast for research and workflow automation.
Pricing
$3.00 / 1,000 data records
Rating
0.0
(0)
Developer
kane liu
Actor stats
0
Bookmarked
10
Total users
4
Monthly active users
10 days ago
Last modified
Categories
Share
India Government Data Search
Search India-focused public data across business, construction, health, and legal products in one run.
- ✅ Search 24 India-focused SIP data products with one keyword list
- ✅ Cover company data, contractor and land records, health catalogs, clinical resources, and legal/judiciary materials
- ✅ Use it without coding, or connect it to ChatGPT, Claude, MCP, Make, Zapier, or n8n
- ✅ Turn categories on only when you need them
- ✅ Free $5 Apify credit is enough to test real searches before you pay anything
India public data is spread across many systems: MCA, RBI, Startup India, CPWD, DDA, land-record and planning resources, CDSCO, CTRI, HMIS, NMC, India Code, Supreme Court, and eCourts. This Actor gives you one search layer across those India-focused products, then returns structured results in one dataset you can review, export, or feed into downstream workflows.
This Actor is best for discovery, topic scanning, monitoring, and early-stage research. It is not a substitute for deep source-by-source compliance analysis, and it does not turn all Indian public data into one perfectly standardized national master database.
What you can do with it
1. Search India company, registration, and financial-entity data
If you are doing business research in India, start with the business category.
What you enter
- Search terms like
Tata,Infosys,Mumbai,NBFC,MSME - Keep business & company data enabled
What you get back
- MCA company master matches
- RBI NBFC and ARC register matches
- RBI cancelled-register matches
- Startup India recognition trend matches
- Udyam registered-unit matches
This is useful when you want a fast answer to questions like:
- Does this company or entity appear in India registration data?
- Is there a relevant NBFC or ARC record?
- Are there MSME or startup-linked public signals worth checking further?
2. Search contractor, land, and planning-related public data
If your topic is procurement readiness, land administration, planning, or contractor verification, the construction category gives you a broad first-pass entry point.
What you enter
- Search terms like
contractor,Delhi,planning,land parcel,CPWD - Keep construction & land records enabled
What you get back
- CPWD enlisted and debarred contractor records
- DDA registered contractor matches
- DILRMP cadastral progress records
- ULPIN metadata matches
- Bharat Maps, Bhuvan, and planning-catalog style entries
This works well when you want a combined view of contractor + planning + land-record context without checking each portal one by one.
3. Search India health, regulatory, and clinical resources
The health category is useful when you want public-data signals across hospitals, catalogs, pricing, and clinical resources.
What you enter
- Search terms like
paracetamol,oncology,hospital,trial,drug price - Keep health & pharmaceutical data enabled
What you get back
- CDSCO catalog matches
- CTRI registry-resource matches
- HMIS catalog entries
- Hospital-directory catalog entries
- NMC register package entries
- NPPA therapeutic price catalog entries
This is useful for healthcare discovery, pharmaceutical transparency research, and early public-data sourcing.
4. Search India legal and judiciary materials
Legal is off by default, but it can be enabled when you want legislation and judiciary-oriented public sources in the same run.
What you enter
- Search terms like
competition,tax,public order,environment,landmark judgment - Enable legal & judiciary data
What you get back
- India Code act-search results
- India Code act-detail results when the query resolves appropriately
- Supreme Court landmark judgment summaries
- eCourts portal resource entries
- Supreme Court Reports portal resource entries
This is useful when you want to connect statutes, court resources, and judgment summaries in one search pass.
5. Connect India public-data discovery to AI or automation
This Actor works for manual use, but it is also designed to plug into broader workflows.
What you enter
- Search terms and category toggles in Apify
- Or the same parameters through API, MCP, or automation tools
What you get back
- Structured records in the dataset
- Stable SIP metadata fields such as
_product_id,_source,_search_term, and_collected_at - Output that is easy to export, summarize, monitor, or pass into spreadsheets and AI agents
This is the right pattern when you want search once, reuse everywhere.
How to use
You do not need to write code to use this Actor.
- Open the Actor and click Try for free
- Enter one or more search terms such as
Tata,contractor,pharmaceutical, orIndia Code - Choose which categories to include:
- business & company data
- construction & land records
- health & pharmaceutical data
- legal & judiciary data
- Set max results per source
- Run the Actor
- Review the results in Apify or export them as JSON, CSV, Excel, XML, or RSS
By default, business, construction, and health are enabled. Legal is available when you want a broader public-source scan.
What you get back
The Actor returns structured records from the selected India-focused products. Exact fields vary a lot by source, because an MCA company record, a CPWD contractor entry, a CDSCO catalog resource, and an India Code act record are not the same kind of object.
Common SIP metadata fields include:
| Field | What it means |
|---|---|
_product_id | The SIP product that returned the record |
_source | Human-readable source label |
_search_term | The keyword that produced the record |
_collected_at | UTC collection timestamp |
In the Output tab, the default overview highlights fields such as:
nametypestatestatus_source_search_term_collected_at
Depending on the enabled category, you may also see fields like:
business_namelicense_idstatedistrictcontractor_nameauthoritycategory_namecase_nameshort_titledecision_datesource_url
Here is a simplified example:
[{"business_name": "TATA CONSULTANCY SERVICES LIMITED","license_id": "L22210MH1995PLC084781","status": "ACTIVE","state": "mh","_product_id": "in_mca_company_master_search","_source": "mca_company_master_search","_search_term": "Tata"},{"contractor_name": "ABC Infra Projects","state": "Delhi","status": "active","_product_id": "in_cpwd_enlisted_contractors","_source": "cpwd_enlisted_contractors","_search_term": "contractor"}]
The goal is not to force every India source into identical semantics. The goal is to make cross-source discovery fast enough to act on.
Coverage
This Actor currently searches 24 India-focused SIP data products across 4 categories:
| Category | What is included | Count |
|---|---|---|
| Business | MCA, RBI NBFC/ARC, Startup India, Udyam | 5 |
| Construction | CPWD, DDA, land-record and planning products, Bharat Maps, Bhuvan | 8 |
| Health | CDSCO, CTRI, HMIS, hospital directory, NMC, NPPA | 6 |
| Legal | India Code, Supreme Court resources, eCourts | 5 |
There are two important boundaries to state clearly.
First:
- These are 24 SIP data products, not 24 completely separate Indian institutions
- Some products are direct record-style datasets
- Some are catalogs, resource indexes, or public portal references rather than row-level operational databases
Second:
- Some products return entity or record-style data like MCA company matches or CPWD contractor entries
- Some return catalog or resource metadata like hospital directory catalogs, HMIS catalog entries, CDSCO catalog resources, or eCourts portal resources
- Some return legal or document-discovery data such as India Code search results or Supreme Court summaries
So the right mental model is: this Actor is an India public-data discovery layer across multiple source types, not a single fully standardized Indian government master database.
Pricing
This Actor is currently listed on Apify with pay per usage pricing.
That means your cost depends on:
- your Apify plan
- how often you run the Actor
- how many results you return
- how many categories and sources you enable
For the current pricing page, see:
In practice, the free Apify credit is enough to test real searches, inspect the shape of the output, and decide whether this workflow fits your research or automation use case before you pay anything.
Connect to your tools
You can use this Actor manually or connect it to your stack.
| Tool | How to use it |
|---|---|
| Apify Console | Run it directly with a form input |
| Make.com | Use the Actor via Apify integration |
| Zapier / n8n | Trigger runs and send results into downstream workflows |
| ChatGPT / Claude | Connect through Apify MCP |
| Scripts / apps | Call it through the Apify API |
If you want to use it with AI workflows, Apify MCP is usually the cleanest path.
When to use something else
This Actor is a strong fit when you want a broad India public-data entry point across company, land, health, and legal topics.
Choose something else if you already know you need a narrower or deeper workflow:
- Use a company-registry-specific workflow if you need deep MCA or corporate-compliance analysis
- Use a construction or land-record specific workflow if you need parcel-level, permit-level, or state-specific land operations
- Use a legal-specific workflow if you need full legal research depth instead of mixed public-source discovery
- Use a health-specific workflow if you need curated medical or pharmaceutical analysis beyond catalog and registry discovery
In short, this Actor is best for finding relevant India public data quickly, not for replacing every source-specific operational workflow.
FAQ
Q: Does this search all Indian government data?
A: No. It searches 24 India-focused SIP data products across 4 categories. That is broad coverage, but not the whole Indian public-data universe.
Q: Are all 24 sources fully independent operational databases?
A: No. The 24 count includes catalogs, resource indexes, and public-source products as well as record-style datasets.
Q: Does it support company, contractor, health, and legal searches in one actor?
A: Yes. That is the core point of the actor. You can mix categories in one run.
Q: Can I get state-level context in the output?
A: In some products, yes. The Output view includes state when the upstream source exposes it.
Q: Can I export the results?
A: Yes. Apify datasets can be exported in formats like JSON, CSV, Excel, XML, and RSS.
Q: Is this only for developers?
A: No. It can be run directly in Apify with form inputs, and the developer-oriented examples are tucked into collapsible sections.
Related Actors
If you are building a broader APAC or public-data workflow, these may also fit:
| Need | Actor |
|---|---|
| Singapore public-sector data | Singapore Government Data Search |
| Australia public-sector data | Australia Government Data Search |
| Global company registries | Global Company Search |
| Japan public-sector data | Japan Government Data Search |
More actors: apify.com/lentic_clockss
Also Available
- Direct API:
https://opendata.best/api/v1/data - Postman collection: Fork and test
- GitHub: Collection source files