SAM.gov Entity Registry

SAM.gov Entity Registry is the General Services Administration's official register of every organization registered to do business with the United States federal government, delivered by Datadory as typed, joinable rows. Registration is mandatory for receiving federal contracts or financial assistance, so the register is not a curated directory - it is the closest thing federal contracting has to a census. Each registration carries a twelve-character Unique Entity ID, a CAGE code, legal and doing-business-as names, structured physical and mailing addresses, registration status with effective and expiration dates, a purpose code, socioeconomic business types and the full set of NAICS and Product Service Code assertions the entity declares for itself.

Scale, concretely: hundreds of thousands of active registrants worldwide, and because support-services trades dominate facility contracting, the industry's core codes - janitorial (561720), security guards and patrol (561612), temporary help and staffing (5613xx), facilities support (561210) - surface vendor subsets in the tens of thousands. Filter by code, state, status, purpose or business type, and every result still keys back to one durable identifier.

Get a sample of this dataset and we route rows scoped to your NAICS cuts, states or named accounts.

One row per registration, exactly as it lands in a delivery:

# captured row - exactly as recorded during the August 2026 research pass
ueiSAM              : ZQGGHJH74DW7      cageCode   : 855J5
legalBusinessName   : IBMCorporation    (concatenated as captured)
samRegistered       : Yes               registrationStatus : Active
registrationDate    : 2018-07-24        purpose     : Z2 (All Awards)

# documented shape - illustrative rows in the delivered frame (placeholders)
ueiSAM              : <12-character unique entity id>   cageCode : <5-char code>
legalBusinessName   : <registered legal name>           dbaName  : <trading name>
status              : A (Active) | E (Expired)          lastUpdate : <date>
registered          : <effective date>   expires : <expiration date>
purpose             : Z2 all awards | Z1 federal assistance only
primaryNaics        : 561720            pscList   : <declared product service codes>
naicsList           : [<codes> + per-code SBA small-business flags]
businessTypes       : <small business | veteran-owned | ...>
physicalAddress     : <addressLine1/2, city, state, zip+4>  district : <congressional district>
exclusionStatusFlag : Y marks an active debarment record

Read the anatomy rather than the angle brackets. Every record resolves through one twelve-character identifier to its CAGE code, its legal and trading names, its status, its effective and expiration dates, its purpose, its declared NAICS and PSC classifications and a structured address with a congressional district attached. The top row is the single registration captured live during research - concatenated legal name included, which deliveries clean up - and it shows the grain honestly: one entity, one identifier, one purpose code, dates attached.

Get a sample of this dataset and real rows arrive in exactly this frame, cut to whichever codes, states or companies you nominate.

Twenty-five verified fields, all defined in the dictionary above. Three do the analytical heavy lifting. ueiSAM is the join key for everything - stable across years and shared with every other federal table keyed on entity identity, which is why panels built here bolt onto award ledgers and enforcement records without fuzzy matching. registrationStatus paired with registrationExpirationDate converts a static directory into a churn map: expired means currently ineligible for new awards, and the expiry column says who crosses that line next quarter. And naicsList keeps every declared code with its SBA small-business flag rather than flattening to a primary, so a firm running both guarding and janitorial operations stays visible in both markets.

The quieter columns earn their place too. purposeOfRegistrationCode splits contract bidders (Z2, All Awards) from grant-seekers (Z1, Federal Assistance only). exclusionStatusFlag surfaces active debarments inside the row instead of requiring a second lookup. pointsOfContact publishes names and titles while keeping phone and email FOUO, and integrityInformation carries the proceedings and responsibility records formerly known as FAPIIS - compliance texture most vendor lists never ship.

• Geography: worldwide by design - any organization registered for US federal business qualifies, whether it operates in Ohio or Osaka. Addresses ship as structured sub-fields down to ZIP+4 and country, and the congressionalDistrict column resolves domestic registrants to district level, which is what lets a territory map or a district-scored model key off the same rows.
• Temporal: registrations are current-state records carrying four dates each - effective, activation, expiration, last update - and historical records are retained for expired registrations, so when a vendor lapsed is reconstructable rather than lost. Renewal happens on entity-driven cycles, which is why the expiration column distributes across the calendar instead of clustering.
• Granularity: one row per entity registration, with establishment-level address structure and multiple NAICS and PSC codes preserved per entity. Deduplicate on UEI when an organization registers for more than one purpose - the code tells you which registration is which.

Set against the wider catalog, where the average quality score across all 1,744 datasets is 7.81, this record scores 8/10: verified field documentation and census-grade coverage, docked only because the total active count is not officially published anywhere and must be measured rather than quoted.

API, files, or your warehouse. Daily, weekly, or hourly.

Your cadence runs independently of the registry's own rhythm. Take a one-time snapshot of a NAICS slice, or keep a warehouse table current so newly activated registrations, fresh expirations and status flips diff cleanly into yesterday's rows - week-over-week comparisons show movement instead of overwriting it. Deliveries arrive normalized to the field dictionary above: statuses and purpose codes decoded, dates typed, the full naicsList array intact rather than truncated to the primary code, and UEI joins preserved so anything else you bolt on keys cleanly.

• Federal-market prospecting - pull the registered universe for a support-services code, filter to active status, rank by region and firm profile, and hand sales a call sheet that already knows who can bid. Written up on our sales growth teams use cases page.
• Renewal-timing outreach - registrations nearing expiration mark vendors facing a hard deadline, the best conversation opener in GovCon sales.
• Vendor eligibility screening - procurement and facilities teams read status, purpose and the exclusion flag before awarding site access, badges or contracts.
• Supply-base market sizing - active-registrant counts per NAICS code per state put a census number under federal TAM models; see our market researchers use cases.
• Competitor registration tracking - which rivals are registered, under which codes, and when those registrations lapse (competitive intel product teams use cases).
• Verification pipelines - journalists, academics and diligence teams confirm contractor claims against the authoritative record, expired history included.

Developers building data products round out the list: typed rows keyed on UEI and CAGE load into onboarding and enrichment backends without transformation gymnastics (developers builders use cases).

Two personas rate highest-fit. Sales and growth teams get the rarest thing in federal prospecting: a complete universe of who can bid, with eligibility and expiration timing already computed. Developers and builders get typed, UEI-keyed rows that wire straight into procurement apps and onboarding flows. Next tier at 2/3: competitive intelligence teams monitoring rivals' registrations and lapses, data scientists assembling the federal-vendor panel by joining UEI and CAGE keys onto other registries, market researchers sizing the federal support-services market off a census rather than a sample, and journalists and academics verifying contractor claims against the register of record. Investors and quant researchers draw narrower value - confirmation of a target's active registration during diligence - and land at 1/3. Persona playbooks sit on the sales growth teams and developers builders pages.

This record owns the who-can-sell layer: every organization eligible for US federal work, identified to a UEI and CAGE code with live status attached. Its neighbors measure different layers of the same industry. Statistics of U.S. Businesses (SUSB) counts firms and establishments by size class but names no vendor - its 2022 file records roughly 215,000 firms in NAICS 5617 services to buildings and dwellings, about 149,000 of them under five employees, which is exactly the fragmentation signal to apply before working a NAICS-filtered registrant list. QCEW — NAICS 56 prices the workforce by county each quarter; OEWS support occupations prices it by occupation; OSHA Enforcement & Injury Data attaches safety records to the establishments behind the registrations; SEC EDGAR Full-Text Search API isolates the publicly traded competitors inside any slice. Practical stacks run them together: this register supplies the denominator of eligible vendors and everything else supplies the numerators. When the question needs award dollars rather than eligibility, switch to the SAM.gov Entity Registration & Contract Awards record - same system of record, transaction-level money attached.

Four things, stated plainly.

First, classifications are self-declared. Entities assert their own NAICS codes, PSC codes and business types, so treat them as claimed position rather than audited certification - and keep the full naicsList, because a facilities firm declaring both 561210 and 561720 belongs in both markets.

Second, counts are photographs. The total of currently active registrants is not officially published anywhere, and this page's figures describe documented scale, not a standing measurement. Any market-sizing figure should be recomputed from your own rows - which a per-registration ledger makes straightforward.

Third, deduplicate on UEI. Organizations register for different purposes - all awards versus assistance only - and purpose codes tell you which registration is which, so naive name-matching double-counts.

Fourth, the two halves of federal vendor data move on different clocks. Registrations renew on entity-driven cycles while awards post as agencies obligate; pair this record with the contract-awards ledger when the question needs both, and let each half carry its own dates. Name your NAICS cuts, states and accounts, and the sample ships shaped to that scope in the schema shown above.