Developers
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.
- Interfaces
- 3
- REST, WebSocket, webhooks
- Latency
- Real time
- Event to webhook
- Rate limit
- Per plan
- Raisable on request
- Versioning
- Dated
- No breaking changes in place
01
Interfaces
REST
Spaces, sessions, events, violations, and payments. 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 for seven days from the console.
SDKs
TypeScript, Python, and Go, generated from the same OpenAPI spec that documents the API.
Sandbox
A full simulated deployment with synthetic occupancy traffic. Build the integration before hardware ships.
02
Built to be integrated, not replaced
Most deployments keep an existing permit system, an existing GIS layer, and an existing 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 | 24 h, backoff |
| Replay window | 7 days |
| GIS | GeoJSON, Esri |
| Sandbox | Free, unlimited |
03