Turn a flow into an API.
Live, never copied.
Any read-only flow can answer requests: a vendor, a partner agency or your open-data portal asks for data, and SentraBridge reads it from the source right then, shapes it, and answers. Nothing is staged in between.
GET /public/data/city-of-demo/permits?status=issued&limit=2{ "data": [
{ "permit": "B26-01182", "type": "Residential solar", "issued": "2026-11-09" },
{ "permit": "B26-01177", "type": "Re-roof", "issued": "2026-11-08" }
],
"next": "/public/data/city-of-demo/permits?status=issued&limit=2&offset=2" }| Access | public, or per-app keys |
| Docs | OpenAPI 3, generated |
| Limits | rate limits · CORS list |
| Kept | counts per call, never the answer |
Straight from the system of record.
Start a flow with “When someone asks for data”, then read, filter, map and protect fields as usual. Each request runs the flow live and returns JSON with paging. Query parameters you declare, like ?status=issued, flow into the steps.
- Paging with next links
- Declared query parameters only
- Flows that write or send are refused
Public for open data, keys for partners.
Mark an API public for open data, or give each partner its own key, shown once and stored only as a fingerprint. Rate limits, an allowed-origins list for browsers, and OpenAPI 3 documentation generated from the answers.
- Per-partner keys you can revoke
- Rate limits and CORS
- Each call logged as counts, never contents
openapi: 3.0.3
info: { title: Permits API }
servers: [{ url: https://permits.city.gov/api }]
components:
securitySchemes:
key: { type: apiKey, in: header, name: X-Api-Key }
paths:
/permits: { get: ..., post: ... }
/permits/{id}: { get: ..., put: ... }
/inspections: { get: ... }| resource | read | write |
|---|---|---|
| Permits | list · get | create · update |
| Inspections | list | — |
Questions, answered
Does this replace our open-data portal?
No. It feeds it, or answers directly when a portal or app needs live data. SentraBridge still connects to Socrata and ArcGIS Hub when you'd rather publish datasets there.
Is the data cached?
Not by default. A flow can turn on a short cache, stored encrypted, for busy public endpoints.
See your own systems connected.
We'll set up a workspace with your systems in a sandbox and build your first flow with you.