Jersey City NJ 311
Sync Jersey City 311 service requests into your warehouse.
The Jersey City NJ 311 connector syncs Jersey City service requests into analytics-ready tables in your data warehouse. Pull service requests, service types and status notes from the Jersey City Open311 GeoReport v2 API on SeeClickFix, with Ingest handling pagination and retries so the tables stay current.
Jersey City NJ 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 Jersey City NJ 311 data in your warehouse or lake, each as its own table on the schedule you pick:
- Service requests
- Request status and closure
- Request types
- Location and district
Authentication
None. The Jersey City 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.
Resources
- Jersey City NJ 311 API documentation: https://seeclickfix.com/open311/v2/465/discovery.json
- Every source Ingest connects
- The tables Ingest creates
- Request Jersey City NJ 311