Connect your workshop software to the same Passport.

Controlled partner access

Access is approved per garage organisation and OAuth application. A registration, VIN or API token alone does not authorise a vehicle. The holder opens the service case and separately approves publication.

Initial access is a time-limited pilot with an agreed organisation and usage allowance. No subscription is charged by this gateway. Production pricing and terms must be agreed before paid access starts.

The integration journey

1. Approve the garage workspace and register its OAuth application.
2. The signed-in holder authorises a service case for a Passport they can access.
3. The garage issues an itemised quote; the holder approves or requests changes.
4. Upload the invoice and service record, then confirm the work.
5. The holder reviews the original documents and explicitly approves publication.
6. Read the published event from the continuing Passport.

PDF, JPEG and PNG originals up to 5 MB. Case lists return up to 50 records with a continuation cursor. No payment or government-data resale is included.

API reference

The OpenAPI contract describes every route, request and error response. The live API remains unavailable until the target environment, approved client and evidence storage have passed acceptance.

Partner authentication uses a short-lived OAuth access token for the approved Platform audience. Keep tokens server-side; never embed credentials in QR codes, links or screenshots. Unattended system-to-system writes are not enabled by a user-token grant.