This endpoint can be used to create a parking session. A successful response indictaes that the associated user/vehicle is authorized to park for the duration specified.
receipt_email parameter is required if Passport is configured to send emails for a Partner.
payment object is required to complete the transaction but the data fields provided may vary depending on your payment integration with Passport. Either the
token field or a
network_token object and the required fields within that object must be provided.
Standard model to provide location information to an API
Represents the payment data used to pay for a parking session.
Depending on the Payment integration with Passport, either you need to send a Passport Payment token in the “token” field or a
network_token object with DPAN, Cryptogram, expiration month-year, and ECI (optional).
network_token is provided, the
provider field is also conditionally required.
The quote to reference when creating the session.
An email address to which the payment receipt will be sent. This is required if Passport is providing receipt emails for a Partner.
Represents a parking session; a distinct instance of a user parking for a period of time.
An ID that represents the individual user who the parking session was created for.
The duration of the parking session, in minutes.
A timestamp that represents when the session ends. Will be in UTC time formatted as an RFC 3339 timestamp.
A machine-readable unique identifier for this session.
An email address to which the payment receipt will be sent.
A human-readable identifier for the session used for identifying the session to involved parties.
If the zone is space based, this is the space number used by the parking session.
A timestamp that represents when the session was started. Will be in UTC time formatted as an RFC 3339 timestamp.
Represents the status of the parking session at the time of the request.
The total cost of the session, is the sum of all transaction related fees.
The set of transactions that have been applied during the life of this session. Session creation will always be present as the initial transaction.
Represents the key values that identify a vehicle.
Represents a location that an operator desires to apply policies and rates to.