Minneapolis 311
Sync Minneapolis 311 service requests into your warehouse.
The Minneapolis 311 connector syncs Minneapolis service requests into analytics-ready tables in your data warehouse. Pull cases, request subjects and reasons, open and close timestamps, case status, and case coordinates from the City of Minneapolis Public 311 ArcGIS feature service, with Ingest handling pagination and retries so the tables stay current.
Minneapolis 311 is not a certified connector yet. Ingest authors one from the vendor's API documentation when a customer asks for it, runs it against the real API, and only then lists it as deployable. Request it and it moves up the queue.
What you can sync
Ingest lands the following Minneapolis 311 data in your warehouse or lake, each as its own table on the schedule you pick:
- Service requests
- Case status and closure
- Request subject and type
- Case location
Authentication
None. The Minneapolis 311 API is public and needs no credential.
Credentials go into a form, never into a chat, and are held in a secret store under your own path. Only the key NAMES ever reach the control database.