Data Dictionary¶

Tango's Data Dictionary documents the fields you can expect on key resources and what they mean.

If you're looking for how to query/filter/order endpoints, see the API Reference.

Awards¶

Definitive contracts, indefinite-delivery vehicles, other transactions, subawards, and solicitation-level groupings.

• Contracts — Definitive contract awards (consolidated from FPDS and USAspending inputs). Response shaping →
• IDVs — Indefinite delivery vehicles (GWACs, IDIQs, etc.). Response shaping →
• OTAs — Other Transaction Agreements from FPDS. Response shaping →
• OTIDVs — Other Transaction IDVs from FPDS. Response shaping →
• Subawards — Sub-contracts and sub-grants under prime awards; sourced from USAspending/FSRS. Response shaping →
• Vehicles — Solicitation-centric grouping of IDVs. Response shaping →
• GSA eLibrary contracts — Persisted GSA eLibrary contract metadata.

Entities¶

• Entities — Vendors and recipients in federal contracting and assistance; UEI is the canonical identifier (from SAM.gov). Response shaping →
• Exclusions — SAM.gov exclusion records (debarments, suspensions); currency is derived at query time. API reference →

DIBBS¶

• DIBBS — DLA Internet Bid Board System: RFQs, solicitations (RFP/IFB), and awards. Awards are line items — do not sum total_contract_price across rows. API reference →

SBIR/STTR¶

• SBIR/STTR — SBIR/STTR topics and DoD DSIP solicitation cycles; topics link to the opportunity or grant that funds them. API reference →

State & Local — Beta¶

• State & Local — State, local and education solicitations and forecasts; status is Tango-derived, and category scheme tagging is partial. API reference →

eBuy¶

• eBuy — GSA eBuy requests scoped to your own Schedule contracts; status is frozen as eBuy supplied it, so read last_seen. API reference →

Forecasts¶

• Forecasts — Upcoming procurement opportunities from agency feeds (e.g., HHS, DHS) before they appear as SAM.gov solicitations. Response shaping →

Grants¶

• Grants — Grant opportunities from Grants.gov (funding opportunities, not assistance transactions). Response shaping →

Budget — Beta¶

• Budget — Federal-account budget data (requested / enacted / apportioned / obligated / outlayed), joined to FPDS contract activity. API reference → · Exploration guide →

IT Dashboard¶

• IT Dashboard — Federal IT investment records from itdashboard.gov, keyed by Unique Investment Identifier (UII). Response shaping →

Protests and appeals¶

Two different proceedings, kept in two resources: a bid protest challenges an award or a solicitation, and a contract appeal disputes a contracting officer's final decision under a contract already awarded.

• Protests — Bid protest cases from GAO, the U.S. Court of Federal Claims, and SBA OHA, with subordinate dockets. API reference →
• Contract appeals — Contract Disputes Act decisions of the CBCA (2007 onward) and the ASBCA (2010 onward); dockets are an array, and a delisted decision is kept. API reference →

Federal Register¶

• Federal Register — Federal Register documents since 1994, keyed by document number and publication date together; agencies and CFR references are served as the Federal Register publishes them. API reference →

Opportunities¶

SAM.gov contract opportunity and notice data.

• Opportunities — Contract opportunities aggregated by parent. Response shaping →
• Notices — Individual SAM.gov notice records (amendments, updates) under an opportunity. Response shaping →

Reference data¶

Lookup tables and codes used across awards and entities.

• Assistance listings (CFDA) — CFDA program numbers and titles for federal grants/assistance. Response shaping →
• Business types — SAM.gov business type codes (e.g., small business, 8(a), HUBZone). Response shaping →
• MAS SINs — MAS Special Item Numbers (SINs) reference data. Response shaping →
• NAICS — North American Industry Classification System codes. Response shaping →
• Organizations — Unified federal hierarchy (departments, agencies, offices in one tree). Response shaping →
• PSC — Product/Service Codes for federal contracting. Response shaping →

Shared¶

Data structures shared across multiple endpoints via response shaping expands.

• Set-aside codes — Set-aside type codes and descriptions.
• Agencies — Agency fields and expansions as they appear in shaped responses. Response shaping →
• Departments — Department fields as they appear in shaped responses. Response shaping →
• Offices — Office fields, flat aliases, and expansions as they appear in shaped responses. Response shaping →