Parking Session Events

Integration partners who are also parking session providers can send parking session information to Passport and support various use cases within a customer’s environment. Parking sessions are processed in real-time as events and there are three events which have been defined to indicate the lifecycle of a parking session. These events are listed below with individual models detailing the technical field schema.

  • parking_session_started
  • parking_session_extended
  • parking_session_stopped

Integration requirements

Providers must be authorized by the parking operator in order to provide data. More information on Passport’s use of the Client Credentials Grant authorization model described by OAuth 2.0 is available here.

While the event specific documentation defines the schema and required fields, the requirements defined by a customer will determine which data points should be required.

Third-party providers can send the parking events via a real-time API request. Real-time transmission is preferred, and certain use cases, such as enforcement, require real-time transmission. If more than one event needs to be sent to Passport, events of a similar event type can be included into an array of events within a single request.

Use Cases

Issuing parking rights

Passport can generate and update parking rights within our system that are passed along to third-party enforcement providers. For example, if a parker uses a physical meter or mobile parking app to park, Passport provides these sessions to enforcement providers through a single integration; the parking provider will not need to make any changes if the enforcement provider changes or alters their technology.


The parking sessions will be reported in Passport’s client-facing portal so that Passport clients can view consolidated reports on the parking activities in their environment.

Data flow

Once the parker has successfully submitted payment via the device (meter, app, etc), the integration partners should publish a parking_session_started event to Passport’s event API.

If the integration partner’s application supports the extension of an active parking session, a parking_session_extended event should be published to Passport’s event API.

No explicit parking_session_stopped event is required unless there is a pre-mature cancellation of the parking session.