Parking citations to the finance database
A parking vendor's API is read nightly and new citations are upserted into a SQL Server table for revenue reporting.
Plenty of city systems have a REST API but no pre-built connector: a niche permitting add-on, a state reporting portal, a parking vendor or an in-house app. The Any REST / JSON API connection covers them.
Give SentraBridge the base address and how the API signs in, then set paths in each step. Flows read any GET path, write with POST, PUT, PATCH or DELETE, and can read only changes with a changed-since parameter. Like every connection, records pass through in memory.
| resource | read | write | changes only | fields |
|---|---|---|---|---|
| Custom paths | any GET path | POST, PUT, PATCH, DELETE | with a changed-since parameter | Fields from the response |
A parking vendor's API is read nightly and new citations are upserted into a SQL Server table for revenue reporting.
Monthly counts from the city database are posted to a state agency's REST endpoint instead of re-keyed by staff.
Requests from a department's own web app are turned into Sentra 311 requests through the app's API.
Start with Any REST API, then import the vendor's OpenAPI file later to get fields and paging filled in.
Systems cities commonly connect with Any REST, each with its own connector page.
Yes. Any REST/JSON API works with this connection. If the vendor has an OpenAPI or Swagger file, importing it fills in resources, fields and paging.
No sign-in, a Bearer token, an API key header, username and password, and OAuth client credentials.
Use the SentraBridge relay. It runs next to the internal API, calls out over HTTPS only, and needs no inbound firewall ports.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.