SAM.gov Opportunities Scraper — Federal Contract Monitor

Scrape active US federal contract opportunities straight from SAM.gov — the official government system where agencies publish solicitations, sources-sought notices, combined synopses and award notices. Built for GovCon capture teams, small-business contractors, proposal shops and market-intelligence pipelines who need clean, structured opportunity data on a schedule.

What you get — one flat record per opportunity

Field	Description
title, solicitation_number	Opportunity title and solicitation/notice number
notice_type, notice_type_code	Solicitation, Presolicitation, Sources sought, Award notice …
is_active, is_canceled	Lifecycle flags
publish_date, response_date, modified_date	Posting date, offer deadline, last-modified
modification_count	Number of amendments (great for change monitoring)
department, agency, office	Full awarding-org hierarchy
naics_code, classification_code, set_aside	NAICS, PSC, small-business set-aside
contact_name, contact_email, contact_phone	Primary point of contact
pop_city, pop_state, pop_zip, pop_country	Place of performance
description	Full plain-text opportunity description
url	Direct link to the opportunity on sam.gov

Why this one

• Actually returns data. It reads SAM.gov's live opportunity index and returns populated, current records — not empty result sets.
• Keyless and official. Pulls from the official SAM.gov source. No API key required to run; supply an optional public api.sam.gov key only if you want higher request budgets.
• Built to be scheduled. Sort by most-recently-modified and filter on a modifiedFrom window to run it as a recurring monitor that surfaces new and amended notices in your industry.
• Rich by default. Detail enrichment adds NAICS, set-aside, point of contact and place of performance — the fields you need to actually qualify and act on a lead.

Filters

keyword · naicsCode · noticeType · setAside · organizationId (agency) · placeOfPerformanceState · modifiedFrom / modifiedTo · activeOnly · includeDetails · maxItems.

Example input

{
  "keyword": "cybersecurity",
  "naicsCode": "541512",
  "setAside": "SDVOSBC",
  "placeOfPerformanceState": "VA",
  "activeOnly": true,
  "includeDetails": true,
  "maxItems": 200,
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"], "apifyProxyCountry": "US" }
}

Pricing

Pay per result — you are charged for each opportunity returned. Run it ad-hoc or schedule it; you only pay for the opportunities you collect.

Notes

This Actor collects publicly available US federal procurement information for legitimate business-development and market-research use. Use US residential proxy (the default) for reliable access.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.