Single by CAGE

Same record as /api/v1/entities/{uei}, keyed by 5-character CAGE code instead of UEI. Adds a queried_cage field at the top of the response so callers can confirm the match. Useful for legacy DoD systems that key on CAGE.

Parameters

• cage_code (path) - 5-character DLA-issued CAGE code. Normalized: lowercase and surrounding whitespace are accepted and converted to uppercase.

Response

{
  "queried_cage": "53YC5",
  "uei": "C111ATT311C8",
  "registration": { "status": "A", "active": true, "...": "..." },
  "entity": { "legal_business_name": "K & K CONSTRUCTION SUPPLY INC", "...": "..." }
}

Example

curl -H "Authorization: Bearer YOUR_API_KEY" \
  "https://govconapi.com/api/v1/entities/by-cage/53YC5"

Errors: 401, 404 (CAGE not found), 429.

Note: Most entities have one CAGE code. Some large organizations (USPS, large banks) have many - up to 80. The entity.cage_codes array in the response lists all CAGE codes registered to the resolved UEI.

Pro enrichment fields (Pro). When the caller has Pro, the response carries the same enrichment families as /entities/{uei}, FFATA subaward income (sub_revenue_total, top_paying_primes) and FPDS prime contract activity (fpds_obligated_total, fpds_distinct_contracts, fpds_transaction_count, fpds_first_action_date, fpds_latest_action_date), computed against the UEI the CAGE resolves to. See the /entities/{uei} section for worked example and field documentation.