St. Louis MO 311
Government
Sync St. Louis 311 service requests into your warehouse. 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 St. Louis 311 connector syncs Citizens' Service Bureau requests into analytics-ready tables in your data warehouse. Pull service requests, their status and closure, the hierarchical service list and service definitions, and request locations from the City of St. Louis CSB Open311 GeoReport v2 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:
- Service requests
- Request status and closure
- Service list and definitions
- Request location
How it gets built
- Choose St. Louis MO 311 when you set up a pipeline, with the warehouse it goes to and a schedule.
- Ingest reads St. Louis MO 311's documentation, and you choose the tables you want.
- Ingest builds the connector and tests it against St. Louis MO 311 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: ?api_key=. Request a free CSB API key on the City of St. Louis City API sign-up page at https://www.stlouis-mo.gov/government/departments/information-technology/web-development/city-api/sign-up.cfm; it is passed as the api_key query parameter.
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 St. Louis MO 311 connector?
- Not as a finished connector yet. Ingest builds it from St. Louis MO 311's own documentation the first time a customer asks, tests it against the real service, and lists it once it passes.
- Which warehouses can St. Louis MO 311 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.
St. Louis MO 311 API documentation: https://www.stlouis-mo.gov/government/departments/information-technology/web-development/city-api/csb-api.cfm
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.