311 requests to Cityworks
New requests from the city's Open311 endpoint become Cityworks service requests for public works crews.
Open311 GeoReport v2 is an open standard for 311 service requests. Many 311 and resident request systems publish it, so apps and other systems can list service types, create requests and check their status.
SentraBridge reads requests changed since the last run, reads service types and creates new requests through any GeoReport v2 endpoint. That makes it a common bridge between a 311 product and a work order or asset system. Requests pass through without being stored.
| resource | read | write | changes only | fields |
|---|---|---|---|---|
| Service requests | list, read one | create | yes | Request ID, Service code, Service, Status, Description, Address… |
| Service types | list | — | — | Code, Name, Group, Description |
New requests from the city's Open311 endpoint become Cityworks service requests for public works crews.
Changed requests are upserted into PostgreSQL with a map point for reporting and GIS.
Requests logged by another department are posted to the 311 vendor's Open311 endpoint with an API key.
Closed requests are published to the city's Socrata open-data portal nightly.
Systems cities commonly connect with Open311, each with its own connector page.
Open311 GeoReport v2 is an open API standard for 311 service requests: list service types, create a request, and read request status.
Many 311 systems publish a GeoReport v2 endpoint. Ask your vendor for the endpoint address and an API key for creating requests.
Read changed requests on a schedule, map service codes to Cityworks problem types, and create service requests. Write the Cityworks ID back if the 311 system allows.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.