USASpending Federal Awards Scraper
Pricing
from $0.49 / 1,000 awards
One row per US federal award already made, from USASpending.gov: award id, recipient and UEI, amount, awarding agency, period and place of performance. Contracts, grants, loans and direct payments. Filter by agency, state, industry code, amount or date. $0.50 per 1,000 awards.
Free-text search across the award record - the description, the recipient, the award id and several fields this Actor does not return. Each term is a separate search and the rows are pooled. Minimum three characters per term, up to 10 terms. Because the search reaches fields you cannot see in the output, a row can be a genuine hit with the word nowhere visible on it.
Which families of award to search. Federal spending is filed in six families and the service will not mix them in one query, so each one you tick is a separate search and the row budget is split between them. Leave it empty and you get contracts plus grants, which is what most people mean by federal awards.
Total awards to return across every kind of award you ticked. The budget is split between them and whatever one family leaves unused is handed to the next. Hard ceiling 10,000. Keep it low while you are testing - you pay per row.
Limit to awards handed out by these departments, written exactly as the source writes them: "Department of Defense", "Department of Energy", "National Aeronautics and Space Administration". This is the cabinet-level department, not the office inside it - the office still comes back on every row. A name the service does not recognise returns nothing rather than everything.
Match the organisation that received the money - a company name, or a UEI. Partial names work. Several entries widen the search rather than narrowing it.
Two-letter US state codes for where the work was actually done, for example TX or CA. This is not the same as where the recipient is registered - a Virginia contractor doing work in Guam is a Guam row. Note that indefinite-delivery vehicles carry only a country for place of performance - no state and no city - so ticking that award family alongside this filter returns nothing for it.
Two-letter US state codes for the recipient's own address, for example VA or MD. Use this when you want the companies in a state rather than the work in a state.
Drop awards below this figure. Useful for cutting out the long tail of small purchase orders, which is most of the row count on a contract search. Leave it empty and nothing is dropped, including the negative rows that record money being taken back off an award.
Drop awards above this figure. Leave it empty for no upper limit.
Only awards with activity on or after this date, as YYYY-MM-DD. The earliest the service accepts is 2007-10-01 and anything earlier is moved up to it. Read the warning on "Date meaning" below - this window is about when money moved, not about the period of performance on the row.
Only awards with activity on or before this date, as YYYY-MM-DD. Leave empty for today.
What the date window is measured against. "Action date" is when money moved, including a modification to an old award - so a 2019 contract amended last month appears in a window covering last month, still showing its 2019 start date. "New awards only" restricts it to awards first signed inside the window, which is what you want for a feed of new business.
Six-digit NAICS codes, such as 541512 for computer systems design. Contracts and IDVs carry these; grants and other assistance mostly do not, so a NAICS filter on a grant search will return very little.
Four-character PSC codes such as R425 for engineering support or D310 for IT services. Contracts only - this is how the government classifies what it bought.
Programme numbers such as 93.778 or 20.205, for grants, loans, direct payments and other assistance. This follows one federal programme across every award it has ever made, which is the tightest filter here. Contracts have no assistance listing, so this will return nothing on a contract search.
Look up specific awards by the id printed on them, for example W912DQ24C4003. An id that does not exist returns an uncharged row saying so, not a wrong match.
Biggest awards first, or most recent first. Either way you get the top of that ordering, so if you ask for 100 rows on a search that matches 40,000 you get the 100 largest or the 100 newest - not a random hundred.
Leave this empty unless you want the requests to go through proxy servers of your own. Add each one as http://user:pass@host:port.
