Skip to main content
Version: 1.0.0

Parkeze Metadata API

Parking sensor data API providing real-time occupancy information, sensor management, and administrative functionality.

Data Model Overview​

The Parkeze platform organizes parking data in a three-tier hierarchy:

Operators​

Operators are parking management organizations (e.g., universities, municipalities, private companies) that own and operate parking facilities. Each operator:

  • Has a unique identifier and display name
  • Manages one or more parking zones
  • May be public (accessible to mobile apps) or private (restricted to specific integrations)
  • Has an associated authentication realm for operator-specific access

Zones​

Zones are geographical parking areas managed by an operator (e.g., "Lot A", "Structure 3", "Street Parking District"). Each zone:

  • Belongs to exactly one operator
  • Contains one or more parking sensors
  • Has a defined boundary (GeoJSON polygon)
  • Tracks occupancy limits and current availability
  • May use sensor-based or non-sensor occupancy methods

Sensors​

Sensors are individual parking space monitoring devices. Each sensor:

  • Belongs to exactly one zone (and by extension, one operator)
  • Has a physical location (latitude/longitude)
  • Reports real-time occupancy status (occupied/vacant)
  • Includes static metadata (space number, installation date, hardware info)
  • May be in maintenance mode or offline

Query Pattern: Most endpoints allow filtering by any of these levels:

  • By operator: Get all data for an operator's zones and sensors
  • By zone: Get all sensors within a specific zone
  • By location: Get zones/sensors within a radius of a point (may span multiple operators)

Authentication​

Security Scheme Type:

http

HTTP Authorization Scheme:

bearer

Bearer format:

JWT

Contact

Parkeze Support: support@parkeze.com