CPPP India Tender Scraper

Extract CPPP India procurement notices for tender discovery, buyer research and procurement monitoring. CPPP India Tender Scraper collects public information into one complete dataset table, ready to export as Excel, CSV or JSON.

Use search filters, set how many results you need and start the Actor. Search returns the fields made available in this service’s public results.

At a glance	Details
📥 Input	Search filters
📋 Collection modes	Search tender records
📤 Output	One row per record, or a failed row for an unsuccessful input
📄 Pagination	Automatic, up to maxResults while more records are available
🔐 Website login	Not required
💾 Export	One dataset view with all fields; Excel, CSV and JSON

What the CPPP India scraper collects 📋

Mode	What you receive
Search tender records	Matching procurement notices and the fields published in the search results.

The field table and complete examples below show the information this Actor returns. Optional values depend on what the source publishes for the selected record.

Coverage for this Actor:

• Browse current Indian procurement tenders from the central or state procurement lists.
• The actor collects public list records only. Tender detail pages, documents and the website’s keyword search are outside its coverage.

How to scrape CPPP India 🚀

1. Choose Search tender records.
2. Complete the search filters.
3. Set Maximum results. The minimum is 1.
4. Start the Actor and review the saved dataset.
5. Export the results or connect them to your workflow.

Search tender records — input example

{
  "mode": "search",
  "listingType": "central",
  "maxResults": 10
}

maxResults limits all saved rows for each search or supplied record, including a failed row. It does not guarantee that the source has that many matching records.

CPPP India data fields and complete output 📦

Each result stays in one row. Every returned field appears in the same dataset view, including list fields and additional published facts. Fields unavailable for a particular record remain empty.

Field	Included data
result_type	Selected collection mode.
input	Submitted search settings, record link or record number.
status	Collection outcome.
error_code	Failure category for an unsuccessful input.
error_message	Readable explanation for an unsuccessful input.
record_id	Stable public notice or tender-lot identifier.
url	Public source notice link.
title	Published notice title.
published_at	Source publication date and time.
deadline	Submission deadline with the advertised time zone.
opening_date	Advertised tender opening date.
reference_text	Original combined title, reference and tender identifier.
buyer	Contracting authority or procuring organisation.
corrigendum	Published corrigendum indicator.
listing_type	Selected source collection, such as contracts, opportunities, central tenders or state tenders.
location	Place of performance or published region.
additional_fields.name	Names of additional published fields, when present.
additional_fields.value	Their corresponding values in the same order.

The complete result below is included for every mode. Text and lists are not shortened. These are examples from validation runs; the source can change.

Search tender records — complete JSON result

{
  "result_type": "search",
  "input": "{\"listingType\": \"central\"}",
  "status": "success",
  "record_id": "central:14160694",
  "url": "https://eprocure.gov.in/cppp/tendersfullview/MTQxNjA2OTQ=A13h1OGQ2NzAxYTMwZTJhNTIxMGNiNmEwM2EzNmNhYWZhODk=A13h1OGQ2NzAxYTMwZTJhNTIxMGNiNmEwM2EzNmNhYWZhODk=A13h1MTc5MDY5NTc4OQ==A13h1MDQvRUVTTS9EUEQtMy8yMDI2LTI3A13h1MTcwNjgz",
  "title": "04/EESM/DPD-3/2026-27",
  "published_at": "29-Sep-2026 08:30 PM",
  "deadline": "08-Oct-2026 03:00 PM",
  "opening_date": "08-Oct-2026 03:30 PM",
  "reference_text": "04/EESM/DPD-3/2026-27 /04/EESM/DPD-3/2026-27/170683",
  "buyer": "Central Public Works Department (CPWD)",
  "corrigendum": "--",
  "listing_type": "central",
  "location": null,
  "additional_fields.name": [],
  "additional_fields.value": []
}

Input settings ⚙️

Setting	What to enter
What to collect (mode)	Choose the information you need.
Maximum results per search or link (maxResults)	Collect up to this many saved results for each search or record link. Minimum: 1.
Procurement level (listingType)	Choose a value for the selected mode.

CPPP India scraping use cases 🎯

Build a tender or contract shortlist

Search the supported procurement collection and export matching records. Keep deadlines, buyer names and original references together when reviewing opportunities.

Research public buyers

Compare available buyer, supplier and contract information across records. Preserve the published currency and value type when working with amounts.

Monitor published procurement records

Schedule repeated exports and compare stable record IDs to identify newly published notices and changes. A search result is not confirmation that bidding remains open.

Pricing and saved-result behavior 💰

See the Actor’s Pricing tab for the current rate. Under dataset-item pricing:

• Each saved record is one result. Lists and additional details attached to it do not create extra rows.
• A saved failed row is also one billable dataset item. This includes invalid inputs, unavailable records, empty searches and exhausted retries.
• At most one failed row is saved per input. Retry attempts do not create additional dataset rows.
• maxResults caps all saved rows for the input. Duplicate copies of the same input are processed once.

CPPP India scraper API and integrations 🔌

Replace $ACTOR_ID with the ID shown in the Actor’s API tab and $APIFY_TOKEN with your Apify token.

curl -X POST "https://api.apify.com/v2/acts/$ACTOR_ID/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"search","listingType":"central","maxResults":10}'

Use Apify schedules for recurring collection, webhooks for completion notifications, and integrations for Google Sheets, Make, Zapier, cloud storage or your own application.

Reliability and public-data limits ⚠️

Temporary request failures are retried up to five total attempts. Invalid record inputs save a failed row without a website request. Confirmed missing records are not retried unnecessarily. If a later request fails, records already saved remain in the dataset. Normal pagination completion does not add a failed row. Collection stops after two consecutive pages return no new records. Configuration, data-saving or request-scheduling failures stop the run.

CPPP India controls the available records and fields. Search records can contain less information than a full public card. The Actor preserves published values and does not fill missing facts with estimates.

Frequently asked questions ❓

Do I need a CPPP India account?

No. This Actor collects the supported public information without your website login.

Which search filters can I use?

The input form supports procurement level. Only the displayed filters are supported.

How many records can I collect?

Set maxResults to the maximum saved rows you want for each input. The minimum is 1. Collection can finish earlier when the source runs out of results or stops returning new records.

Why are some fields empty?

The source may not publish a value for that record or mode. Optional information remains empty.

Can I export all the fields?

Yes. All returned fields are included in one dataset view. Nested lists remain attached to their parent record.

Support 🛟

For a reproducible issue, share the run ID, selected mode and a safe public example through the Actor’s support channel. Keep tokens, passwords and proxy credentials private.