Background

As a service to data analysts and developers, we are providing flattened time series files concatenating every Monthly Statistical Snapshot table from the December 2012 edition through the latest edition. The files will be updated along with every new monthly release.

The JavaScript Object Notation (JSON) files include publication- and table-specific metadata, including variable naming, relationships, and units, plus sources, notes, or footnotes. Users of the Comma-Separated Values (CSV) files should refer to the JSON files or the latest monthly edition for these details.

These are beta release files. The schema (particularly measure and dimension ids/keys) may change based on:

• user feedback,
• evolving standards from the federal statistical community, or
• development of similar files for other SSA statistical releases.

To provide feedback, email statistics@ssa.gov.

Available Files

• Table 1. Number of people receiving Social Security, Supplemental Security Income, or both
  • monthly_statistical_snapshot_table_1.json
  • monthly_statistical_snapshot_table_1.csv
• Table 2. Social Security benefits
  • monthly_statistical_snapshot_table_2.json
  • monthly_statistical_snapshot_table_2.csv
• Table 3. Supplemental Security Income recipients
  • monthly_statistical_snapshot_table_3.json
  • monthly_statistical_snapshot_table_3.csv

User Notes

• JSON and CSV files can be opened in any text editor or imported into any spreadsheet or data visualization application.
• These files are regenerated every month from the full archive of monthly HTML tables, including any post-release corrections. Errata in 2026 or later will be listed on any affected monthly index page and this page.
• Table 1: The “Other” (other) beneficiary type is not applicable (always null) for the measures “SSI only” (num_ssi_only) and “Both Social Security and SSI” (num_concurrent).
• Table 2: The “Beneficiaries: Percent” (pct_beneficiaries) measure is of type string because the value may be (L) (less than 0.05 percent) and we leave it to end users to determine how best to handle this for their analysis.