Everything the dashboard does, the API does first.
The console is a client of the same public API you get. There is no privileged internal endpoint, which means anything you see, you can build against, and any system you run can be connected.
01
Interfaces
REST
Vehicles, rights, sessions, citations, payments and occupancy. Cursor pagination, idempotency keys, and typed errors throughout.
WebSocket
Subscribe to occupancy changes by zone or by space. Used for live maps and wayfinding signage.
Webhooks
Signed, retried with exponential backoff, replayable from the console.
Connector SDK
Facts in, actions out. A connector maps a vendor's data onto the ontology and carries out the actions it supports, tested against a simulated platform.
Sandbox
A simulated deployment with synthetic traffic. Build the integration before hardware ships.
02
Built to be integrated, not replaced
Most deployments keep an existing permit system, GIS layer and finance stack. Parkeze is designed to sit between them rather than ask them to move.
| Spec | OpenAPI 3.1 |
| Auth | API key, OAuth 2 |
| Pagination | Cursor |
| Idempotency | Supported |
| Webhook retries | Backoff |
| GIS | GeoJSON, Esri |
| Connectors | Python SDK |
03