Census QWI
Government
Sync Quarterly Workforce Indicators from the US Census Bureau. Ingest builds this connector the first time a customer asks for it, then keeps the tables current in a data warehouse you own, on the schedule you choose.
The Census QWI connector syncs Quarterly Workforce Indicators into analytics-ready tables in your data warehouse. Pull employment, job creation, earnings, and turnover series by geography, industry, and worker demographics from the Census Bureau API, with Ingest handling auth, pagination, and retries so the tables stay current.
What you would get
Each of these arrives as its own table, kept current on the schedule you choose:
- Employment and job flows
- Earnings
- Hires and separations
- Industry and geography breakdowns
How it gets built
- Choose Census QWI when you set up a pipeline, with the warehouse it goes to and a schedule.
- Ingest reads Census QWI's documentation, and you choose the tables you want.
- Ingest builds the connector and tests it against Census QWI itself.
- A person at Ingest reviews and publishes it, and your pipeline starts on its own.
What you will need
API key, sent as a query parameter: ?key=. Request a free Census Bureau API key; it is emailed and activated by a confirmation link.
You enter it once, in a form in Ingest, and it is kept in a secret store set aside for your organization.
Questions
- Does Ingest have a Census QWI connector?
- Not as a finished connector yet. Ingest builds it from Census QWI's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
- Which warehouses can Census QWI data go to?
- Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
- Do I need to write code?
- No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.
Census QWI API documentation: https://www.census.gov/data/developers/data-sets/qwi.html
Where this would land, and what else connects
Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.
Other sources Ingest connects for government teams: Abilene TX 311, Albany NY 311, Ann Arbor MI 311, Anne Arundel County MD 311, Auburn WA 311, Aurora IL 311.