Single by UEI

Single SAM-registered entity by UEI. Returns the registration block (status, expiration, dates) and the entity block (legal name, address, NAICS, PSC, business-type certifications, CAGE codes). Available on any plan (including the free trial); Pro subscribers can use /api/v1/companies/{uei} for the same data merged with award history.

Parameters

• uei (path) - 12-character SAM Unique Entity Identifier. Normalized: lowercase, mixed case, and surrounding whitespace are accepted.

Response

{
  "uei": "XX2WFHJEFB45",
  "registration": {
    "status": "A",
    "active": true,
    "registration_date": "2001-08-16",
    "activation_date": "2026-01-21",
    "expiration_date": "2027-01-19",
    "expiring_soon": false,
    "source_extract_date": "2026-04-05"
  },
  "entity": {
    "legal_business_name": "KAMPI COMPONENTS CO INC",
    "dba_name": null,
    "entity_structure_code": "2L",
    "entity_url": "www.kampi.com",
    "physical_address": {
      "street1": "...", "city": "FAIRLESS HILLS",
      "state": "PA", "zip": "19030", "country": "USA"
    },
    "primary_naics": "423990",
    "naics_codes": ["423990Y", "332710Y", "..."],
    "psc_codes": ["...", "..."],
    "business_types": ["2X", "XS"],
    "business_types_labels": [
      "For Profit Organization",
      "Subchapter S Corporation"
    ],
    "cage_codes": ["7Z016"]
  }
}

Example

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

Errors: 401 (no auth), 404 (UEI not in current SAM data), 429 (rate limit).

Not every valid-shape UEI is in the registry

A 12-character UEI passing format validation can still 404 here. Reasons include: the entity has expired its SAM registration and dropped out of the public extract; the UEI was issued for a registration that never completed; it's a non-public or excluded entity. We carry ~885K firms (the public V2 monthly snapshot, as of 2026-07-10). Expect a non-trivial 404 rate when batch-looking-up UEIs from external lists. If you need only firms currently active in SAM, append ?active_only=true to /api/v1/entities/search instead.

Use cases: compliance checks before contract signing (registration.active + registration.expiration_date), CRM enrichment, vendor-onboarding form auto-fill, set-aside qualification preview (entity.business_types_labels).

Pro enrichment fields (Pro)

When the caller has Pro, two families of enrichment fields are added inline alongside the SAM data. Fields are omitted entirely on non-Pro keys; existing non-Pro integrations see exactly the SAM record above.

FFATA subaward income: what this UEI received as a sub-vendor:

• sub_revenue_total: sum of FFATA dollars received as a sub-vendor within current subaward coverage (FY2025 + FY2026 today; window scales as backfill lands).
• top_paying_primes: up to 10 {uei, name, total, subaward_count} objects, sorted desc by total.

FPDS prime contract activity: what this UEI has been awarded directly as a prime:

• fpds_obligated_total: sum of federal action obligation across every FPDS transaction for this UEI in the FY2025-onward window (since 2024-10-01).
• fpds_distinct_contracts / fpds_transaction_count: count of distinct contracts and total transactions (base awards + every modification).
• fpds_first_action_date / fpds_latest_action_date: ISO date bounds.

SBA small-business profile (sba_profile): the firm's SBA Dynamic Small Business Search (DSBS) record. Like the two families above, it is Pro-gated inside this any-plan endpoint, present only for a Pro caller and omitted entirely (no teaser) on Developer or free keys. When present it always states which case you are in: {"in_dsbs": true} with the full block (small_business NAICS-small determination, verified certifications with entrance_date / exit_date / status, self-asserted self_certifications kept separate, capabilities, firmographics), or exactly {"in_dsbs": false} when the firm has no DSBS profile (common: large primes never appear in DSBS, and DSBS covers roughly half of SAM entities). When a profile is present, _sources gains sba_dsbs. Every field is named in full on the SBA small-business profile (DSBS) reference page.

Field shapes are documented once at the top of the Endpoints section under Pro enrichment fields (universal pattern).

Worked example (Pro response, both enrichment families present)

Live GET /api/v1/entities/CKV2L9GZKJK3 excerpt (verified 2026-06-01):

{
  "uei": "CKV2L9GZKJK3",
  "registration": { "..." },
  "entity": { "..." },
  "sub_revenue_total": 126453199.25,
  "top_paying_primes": [
    {"uei": "SMNWM6HN79X5", "name": "GENERAL DYNAMICS INFORMATION TECHNOLOGY, INC.",
     "total": 26501723.69, "subaward_count": 1},
    {"uei": "XDDKMXTVJSN8", "name": "COGNOSANTE MVH LLC",
     "total": 21702000.00, "subaward_count": 1},
    "...up to 10 entries"
  ],
  "fpds_obligated_total": 4179687234.11,
  "fpds_distinct_contracts": 908,
  "fpds_transaction_count": 2808,
  "fpds_first_action_date": "2024-10-01",
  "fpds_latest_action_date": "2026-05-29",
  "_sources": ["sam_entities", "usaspending_ffata", "usaspending_fpds"]
}

For per-record drill-down, use the underlying surfaces: /api/v1/contracts/search?uei=… for every FPDS transaction; /api/v1/companies/{uei}/prime-relationships for every subaward received. The combined prime + sub revenue picture with prime_revenue_share lives on /api/v1/companies/{uei} (also Pro). The bidirectional vendor-risk view (as_prime + as_sub + contract_exposure) lives on /api/v1/vendor-risk/{uei}.