Single contract (by PIID)

Single contract by PIID. Returns the latest transaction (the contract block, 26 lean fields by default) plus a transaction_rollup sibling that aggregates obligations, ceiling, distinct recipients, and action-date bounds across every transaction under that PIID. Pro responses also include a subaward_rollup sibling.

Parameters

piid (path): Procurement Instrument Identifier, upper-cased server-side.
fields: lean / expanded / full / comma list, applies to the contract block. transaction_rollup is fixed shape.

Response

{
  "contract": { "...": "26 lean fields, latest transaction" },
  "transaction_rollup": {
    "transaction_count": 52,
    "total_obligated":   162360657.45,
    "max_current_total_value":   392556695.66,
    "max_potential_total_value": 504348015.85,
    "latest_current_total_value":   392556695.66,
    "latest_potential_total_value": 504348015.85,
    "first_action_date":  "2024-10-11",
    "latest_action_date": "2026-02-27",
    "distinct_recipient_ueis": 1
  },
  "_sources": ["usaspending_fpds"]
}

(latest_current_total_value / latest_potential_total_value are aliases for the max_* pair.)

Reading the numbers

The example above is the live shape for Deloitte's $392M Army task order under PIID W56JSR23F0062. Two customer-actionable signals are in the rollup directly: transaction_count: 52 over a 16-month action-date span says the prime has cycled 52 mods (active, well-managed contract). max_current_total_value and latest_current_total_value agree at $392.56M (current ceiling matches the all-time peak, scope stable). max_potential_total_value at $504.35M agrees with latest_potential_total_value at the same number, but when these two differ in a live response, that is a scope-reduction signal worth chasing in a recompete play (a previous mod set a higher ceiling than the current one). Customers tracking ceilings over time read both pairs and compare.

Errors

404: no contract with that PIID in the coverage window.
429: rate limit exceeded.

Subaward enrichment (Pro)

On Pro keys, the response includes an additional subaward_rollup sibling summarizing the FFATA subaward footprint flowing from this prime contract: sub count, total subcontracted, share of the prime obligation, distinct sub-vendor count, first and last subaward dates, plus up to 5 named top_subs. The PIID join into the subaward layer is dense within the FY2025+ window: roughly 88% of subaward filings match a prime contract row, and 98% of in-scope contracts that have subaward activity see a populated block. _sources extends to ["usaspending_fpds", "usaspending_ffata"] when the block fires. For UEI-keyed reverse lookups across every contract a recipient holds, use /api/v1/companies/{uei}/subawards.

Example

curl -H "Authorization: Bearer YOUR_API_KEY" \
  "https://govconapi.com/api/v1/contracts/W56JSR23F0062"