/census/tables

POST /api/census/tables

Price: 10 credits

Get a U.S. Census table's data by table id, optionally for a specific geography

How to use it

Get the data of a U.S. Census Bureau table (population, income, housing, race, age/sex, etc.) by its table id. Optionally pass a geography FIPS clause to scope to a state, county, or other area. Returns one record per geography (some tables default to a national breakdown across all states, yielding multiple records), each with its geography name and every table variable's human-readable label, concept, and value. Use the 'tables/search' endpoint to find a table id.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• id string required — Census table object id ({DATASET}{Y}{YEAR}.{TABLE}) (examples: "ACSDP1Y2023.DP05", "ACSST1Y2024.S1901", "ACSDT5Y2022.B01001", "DECENNIALPL2020.P1"; minLength: 1)
• geo string nullable — Geography FIPS clause; omit for national level (examples: "040XX00US06", "050XX00US06037", "010XX00US")

Response

• @type string (default: "CensusTable")
• id string required
• table_name string nullable
• geo string nullable
• geo_name string nullable
• data_url string nullable
• metadata_url string nullable
• values array (default: [])
  • @type string (default: "CensusTableValue")
  • variable string required
  • label string nullable
  • concept string nullable
  • group string nullable
  • value string nullable
  • margin string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Table id not found, or no data for the requested geography Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.