Passport
Passport (Passport Labs) is a mobility management platform for cities, universities, and agencies, covering digital parking payments, enforcement, permits, and curbside management, and is used by 800+ agencies. Passport exposes a partner developer program at developer.passportinc.com whose REST APIs let parking apps, navigation apps, in-car infotainment, and mobility/POS systems create and stop parking sessions, quote and determine rates, bulk-export the parking environment (zones, spaces, rules), receive parking event schemas, and manage enforcement immobilizations. Rates and rules are configured once by Passport's customers and pushed to payment providers via API. Access is gated - partners register an application, are issued OAuth client credentials by Passport's identity provider, and only authenticated partner applications may call the public APIs. No SDK is required. Commercial terms are partnership / agency-contract based rather than publicly listed self-serve pricing.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Passport the way a machine reads it — 7 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Passport scores 14.2/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Passport
Each block below is one kind of artifact we hold for Passport. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 5
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Passport Parking Sessions and Quotes API
Quote, create, and stop parking sessions on behalf of a driver in a Passport-managed zone - the core surface behind facilitating a paid parking session from a parking app, navig...
Passport Parking Rates API
Determine the parking rate for a location and duration. Rates are defined uniquely by each Passport customer (city, university, or operator) and vary by location, time, and rule...
Passport Parking Environment Export API
Bulk export of the parking environment. Returns a single-use URL to download a JSON file describing zones, zone numbers, geolocation (latitude and longitude), and associated rul...
Passport Parking Event Schemas
Versioned JSON schemas for the parking events Passport emits to partners (for example a parking_session_started event, v3.0.0). These are server-to-endpoint webhook-style event ...
Passport Immobilizations API
Manage enforcement immobilizations (vehicle boots) - for example updating an existing immobilization record - as part of Passport's digital parking enforcement and compliance wo...
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Passport — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Access & Security 2
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/passport-parking · machine-readable index on apis.io