FPDS Federal Procurement Awards Scraper avatar

FPDS Federal Procurement Awards Scraper

Pricing

from $0.80 / 1,000 record scrapeds

Go to Apify Store
FPDS Federal Procurement Awards Scraper

FPDS Federal Procurement Awards Scraper

Pull federal contract award actions straight from FPDS, the authoritative system of record for US government procurement. Filter by signed/last-modified date range and page through PIID, vendor, dollar value, NAICS/PSC, set-aside type, and parent IDV linkage for every action.

Pricing

from $0.80 / 1,000 record scrapeds

Rating

0.0

(0)

Developer

BowTiedRaccoon

BowTiedRaccoon

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Categories

Share

Pull contract award actions straight from FPDS, the system of record for US federal procurement. Give it a signing-date range and get back vendor names, dollar values, NAICS/PSC codes, set-aside types, and parent contract linkage for every action in that window.


FPDS Federal Procurement Awards Scraper Features

  • Filters by signing date, so you can pull yesterday's awards or a historical month without touching anything else
  • Returns both the action-level dollar value and the total contract value including options
  • Includes the parent IDV/BPA PIID on task and delivery orders, so you can tie an order back to its umbrella contract
  • Captures vendor UEI alongside the vendor name for downstream entity matching
  • Surfaces set-aside type and competition details on every record where FPDS populates them

Who Uses FPDS Award Data?

  • Govcon business development teams — track which primes and subs are winning in a given NAICS code or agency
  • Subcontractor-seeking primes — find vendors already winning adjacent work to approach for teaming
  • Market intelligence analysts — build spend-by-agency or spend-by-vendor views without re-deriving them from the USAspending summary feed
  • Compliance and audit teams — pull the action history behind a specific contract or IDV

How FPDS Federal Procurement Awards Scraper Works

  1. You set a signing-date range (or let it default to the last day) and a maximum number of records.
  2. The actor queries FPDS's public ATOM feed for award actions signed in that window.
  3. It pages through results 10 at a time until it hits your record limit or runs out of matches.
  4. Each action comes back as one flat record — PIID, vendor, dollar values, dates, codes, and the FPDS detail page URL.

Input

{
"maxItems": 100,
"startDate": "2026-10-01",
"endDate": "2026-10-07"
}
FieldTypeDefaultDescription
maxItemsInteger10Maximum number of award action records to return (required)
startDateString1 day before endDateOnly include actions signed on or after this date (YYYY-MM-DD)
endDateStringTodayOnly include actions signed on or before this date (YYYY-MM-DD)

Leave startDate/endDate unset to pull the most recently signed actions. Set both to pull a specific historical window — FPDS's corpus runs back to the early 2000s, so a wide range combined with a high maxItems can return a very large result set.


FPDS Federal Procurement Awards Scraper Output Fields

{
"piid": "0003",
"agency_id": "DEPT OF DEFENSE",
"contracting_office_agency": "DEFENSE LOGISTICS AGENCY",
"vendor_name": "LINDE GAS & EQUIPMENT INC.",
"vendor_duns_uei": "L1P3D635U756",
"obligated_amount": -5564.77,
"base_and_all_options_value": 0,
"signed_date": "2026-10-14 00:00:00",
"effective_date": "2026-10-14 00:00:00",
"completion_date": "2027-04-13 00:00:00",
"contract_action_type": "DELIVERY ORDER",
"naics_code": "325120",
"product_or_service_code": "6830",
"place_of_performance": "FORT WORTH, TEXAS, UNITED STATES",
"set_aside_type": "NO SET ASIDE USED.",
"description_of_requirement": "",
"title": "DELIVERY ORDER 0003 awarded to LINDE GAS & EQUIPMENT INC. for the amount of -$5,564.77",
"modification_number": "0",
"reference_idv_piid": "SP046024D0053",
"detail_url": "https://www.fpds.gov/ezsearch/search.do?s=FPDS&indexName=awardfull&templateName=1.5.3&q=0003+9700+"
}
FieldTypeDescription
piidStringProcurement Instrument Identifier — the unique contract/award ID
agency_idStringAwarding department/agency name
contracting_office_agencyStringContracting office that issued the award
vendor_nameStringName of the awarded vendor
vendor_duns_ueiStringVendor Unique Entity Identifier (UEI)
obligated_amountNumberDollars obligated on this specific action (negative on a deobligation)
base_and_all_options_valueNumberTotal contract value including all priced options
signed_dateStringDate the action was signed
effective_dateStringDate the action takes effect
completion_dateStringCurrent estimated completion date
contract_action_typeStringType of action (delivery order, definitive contract, BPA call, etc.)
naics_codeStringPrincipal NAICS industry code
product_or_service_codeStringProduct or Service Code (PSC)
place_of_performanceStringPrincipal place of performance (city, state, country)
set_aside_typeStringCompetition set-aside type applied to this action, where FPDS records one
description_of_requirementStringFree-text description of the requirement (sparsely populated by FPDS)
titleStringHuman-readable summary of the award action
modification_numberStringModification number for this action (0 for the original award)
reference_idv_piidStringPIID of the parent IDV/BPA this action was placed against, if any
detail_urlStringFPDS detail page for this award action

FAQ

How do I pull a specific date range of federal contract awards?

Set startDate and endDate on the input (both YYYY-MM-DD). FPDS Federal Procurement Awards Scraper filters by signing date, so a one-week range returns only actions signed inside that week — not a sample filtered down after the fact.

What's the difference between this and a USAspending scraper?

USAspending republishes FPDS data as award-level summaries. This actor reads FPDS directly at the action level, so you get every modification, delivery order, and amendment individually — along with set-aside type, PSC, and parent IDV linkage that the USAspending summary drops.

How far back does the data go?

FPDS award actions go back to the early 2000s. There's no built-in limit on startDate; a wide historical range combined with a high maxItems will take longer and return more records, but it's the same query mechanism either way.

Do I need an account or API key for FPDS?

No. FPDS Federal Procurement Awards Scraper needs no credentials — FPDS's award-action feed is public.

Can I filter by vendor or agency?

Not directly as input fields today — every record already carries vendor_name, agency_id, and contracting_office_agency, so filter the output after the run. File an issue if a built-in vendor or agency filter would help your workflow.


Need More Features?

Need a different filter, an additional field, or a bulk historical pull shaped differently? File an issue or get in touch.

Why Use FPDS Federal Procurement Awards Scraper?

  • Direct from the source — reads FPDS action-level data, not a derivative summary, so modifications and amendments show up individually instead of collapsed into one award
  • Built for date-bounded pulls — the signing-date filter is a hard filter verified against the live feed, so a one-day pull returns one day of awards, not a loosely-ranked approximation
  • No account required — FPDS's award feed is public; there's nothing to register for