Government RFP & Tender Monitor

Pricing

Rating

Developer

Actor stats

Categories

Share

What this Actor does

Monitor public government procurement, tender, and RFP listing pages and extract new tenders as clean, structured JSON.

It processes user-provided public URLs (such as national procurement portals, state e-tender pages, or public agency notice boards), prioritizes JSON-LD/schema.org structured data, and can optionally use a conservative fallback that reads visible public tender links and table rows. It normalizes useful fields, applies an optional keyword filter, deduplicates rows by tender URL, and saves structured records to the Apify dataset.

Why this Actor is useful

Suppliers, bid teams, and analysts pay for this kind of extraction because it replaces manual portal checking, creates repeatable daily or weekly monitoring, feeds spreadsheets, CRMs, and bid pipelines, and turns scattered public procurement pages into a clean, API-ready dataset.

Who this is for

• Government suppliers and contractors
• Bid and proposal (RFP) teams
• Procurement and tender consultants
• Construction, IT, and services vendors
• Market intelligence and GovTech analysts
• Trade associations and chambers of commerce
• Researchers tracking public spending

Common use cases

• Track new tenders across multiple government portals
• Filter opportunities by keyword (e.g. "construction", "IT services")
• Feed a bid pipeline or CRM with fresh RFP leads
• Monitor a specific issuing authority or region
• Build recurring public-procurement intelligence datasets

Input

Output

Sample input

{
"startUrls":[
{
"url":"https://example.gov/tenders"
}
],
"keywords":["construction","IT services"],
"maxItems":25,
"maxConcurrency":3,
"extractionMode":"structuredDataWithFallback",
"requestTimeoutSecs":30
}

Sample output

{
"tenderTitle":"Supply and Installation of Office IT Equipment",
"tenderId":"GOV/2026/IT/00471",
"issuingAuthority":"Department of Public Works",
"category":"IT services",
"location":"New Delhi, India",
"publishedDate":"2026-06-15",
"closingDate":"2026-07-10",
"estimatedValue":4500000,
"currency":"INR",
"tenderUrl":"https://example.gov/tenders/GOV-2026-IT-00471",
"documentUrl":"https://example.gov/tenders/GOV-2026-IT-00471/notice.pdf",
"sourceUrl":"https://example.gov/tenders",
"detectedAt":"2026-06-27T00:00:00.000Z",
"extractionMethod":"structured_data",
"confidenceScore":0.95,
"missingFields":[]
}

Pricing

This Actor uses a pay-per-event model: $0.005 per tender result saved to the dataset. You pay only for the structured tender rows you receive, which makes recurring monitoring predictable and low-cost.

How to use

Run this Actor on Apify with public tender portal URLs, export the dataset as JSON, CSV, or Excel, or pull it through the Apify API. Connect the output to Google Sheets, Make, Zapier, a webhook, your CRM, or an internal bid dashboard. For monitoring, save the input as an Apify task and schedule recurring runs to catch new tenders.

Best practices

• Start with a small set of reviewed public procurement URLs.
• Prefer portals that expose schema.org / JSON-LD structured data.
• Use keywords to focus on the sectors or services you bid on.
• Use structuredDataOnly for highest precision; use structuredDataWithFallback for portals that only show visible tender tables.
• Keep maxConcurrency low for smaller portals.
• Review each source website's rules before scheduling recurring runs.

Compliance and responsible use

This Actor is for public data only. It must not be used to bypass logins, paywalls, CAPTCHAs, or security systems, to collect private or sensitive personal data, or to support spam or abuse. Government procurement information processed here should be publicly published tender notices. You are responsible for following applicable laws and each source website's rules.

Limitations

• Output quality depends on the public structured data available on the source pages.
• Fallback extraction is intentionally conservative and only looks for visible public tender/RFP/bid link and table patterns. It does not claim universal portal support.
• Dates and amounts are extracted as published; formats vary by country and portal and are not reformatted or converted.
• Some fields may be empty when the source does not publish them; these appear in missingFields.
• The Actor does not claim support for any specific third-party procurement platform.
• Website markup and access policies can change.

Troubleshooting

• Empty output usually means the page has no public structured tender data and no visible tender-link patterns.
• Invalid URL errors mean one or more input URLs are malformed.
• Slow runs can usually be improved by lowering maxConcurrency.
• Missing fields are source-data limitations, not inferred values.

Changelog

• v0.1.0: Initial release with structured-data-first extraction, conservative public tender-listing fallback, keyword filtering, and confidence scoring.