Session integration

Third-party providers can provide parking session information to Passport to support various use cases for the city. For example, a meter provider could submit parking session information to be transmitted to an enforcement provider.

Integration requirements

Third-party providers can send the parking_session_started event via API as documented here. Real-time transmission is preferred, and certain use cases, such as enforcement, require real-time transmission.

Providers must be authorized by the parking operator in order to provide data. More information on API authorization is available here.

Use cases

Issuing parking rights

Passport can provide third-party parking sessions to 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 operators can view consolidated reports on the parking activities in their cities.

Data flow

Once the parker has successfully submitted payment via the device (meter, app, etc), the provider should publish a parking_session_started event to Passport’s session integration API. If the parker extends an active parking session via the device, the provider should publish a parking_session_extended event to Passport’s session integration API.

No explicit “stop” event is required.