GovCon API
The federal contracting data layer
GovCon API
The federal contracting data layer
Federal contract awards reach public data on two different clocks. Most civilian agencies report an action within a few business days. The Department of Defense and the US Army Corps of Engineers hold their contract awards for 90 days before public release. If you query the last quarter of federal contracting today, the DoD portion is not missing. It has not been released yet.
Two federal source systems carry the record. Contracts flow through FPDS (the Federal Procurement Data System). Financial assistance, meaning grants and similar awards, flows through FABS. Both feed USAspending.gov, the public system of record.
The path for a contract is short. A contracting officer records the action, and procurement policy allows three business days to file the contract action report to FPDS. Once it is filed, the record is made available to USAspending the following morning. USAspending reloads its public dataset daily; as of this writing its awards/last_updated endpoint reports the data current to 07/15/2026.
For civilian agencies, that means an award is typically queryable within a few business days of the action date. This is the timing most people assume applies everywhere. For one large category, it does not.
The single most misread fact about federal contract timing: Department of Defense and Army Corps of Engineers contract awards are published on a 90-day delay. DoD-funded contract awards are withheld from public access for 90 days after the action is reported, an operational-security measure.
What the hold covers: contract award data, subcontract data, and the Account Breakdown by Award (File C and File D1). What it does not cover: account-level obligation data (Files A, B, and D2) stays current, because those files do not identify individual awards.
The consequence is specific. A DoD delivery order signed in March is normally not public until June. A query for "DoD contracts in the last 90 days" will look sparse, then fill in continuously as the hold lifts on each action. That is not incomplete data on your end or ours. It is data the government has not released yet.
This timing is genuinely under-documented. The Government Accountability Office has noted that the 90-day delay for DoD procurement data is not clearly communicated, which is why most data consumers meet it first as an unexplained gap in recent defense activity.
Sources: FPDS DoD data availability, and the USAspending FAQ on the DoD reporting schedule.
Recent-quarter completeness is agency-dependent, so treat "the last few months" differently by source:
The practical rule: filter by action_date, not by "recently added," and expect the most recent 90 days of DoD awards to fill in over the following quarter. If you are trending defense spending, hold the last quarter as provisional.
Two adjacent timing facts are worth carrying, because they shape recent-period counts:
Our federal contract data tracks USAspending's public record and refreshes daily; the contracts source reads current as of 2026-07-13. The 90-day DoD hold is a property of the source, not a choice anyone downstream makes, so the same recent-quarter caveat applies to every dataset built on FPDS, ours included: treat the last quarter of defense contracting as provisional, because much of it has not been released yet. A number that looks low today for a defense NAICS or agency is usually the hold, not the market.
What this page gives you is the timing model stated plainly, with the numbers and the source caveats up front instead of discovered in production. That is the reason it exists.
If you are pulling federal contracts programmatically, the USASpending API guide covers the endpoint quirks, and the GovCon API reference documents the contract and vehicle endpoints directly.
Last updated: July 2026