Skip to content

Vehicle webhooks. Planned access.

Webhooks: purpose and availability

Proposed webhooks would notify an authorised application when a report is ready and identify the relevant vehicle and report. There is no public webhook endpoint or live event subscription to configure today. Use this page to assess the proposed fields and request the workflow you need.

Proposed uses

  • Keep your existing tools

    Plan a connection around the stock or dealer management system your team already uses.

  • React to completed checks

    Start the next internal step once a report is available for review.

  • Match records reliably

    Use report references and vehicle registrations together to keep updates attached to the correct record.

An example workflow

A proposed way to connect Car Check with your own tools.

  1. A report becomes ready

    The proposed event starts from a completed check in your authorised account.

  2. Your application validates it

    Verify the agreed delivery signature and recognise repeated events.

  3. Update your vehicle record

    Store the report reference and queue any internal review actions.

Information for your workflow

Event identifier
A proposed unique identifier for handling repeat deliveries.
Report reference
The report your application should associate with the event.
Registration
The UK vehicle registration used for the check.
Completion time
A timestamp to preserve the order and age of updates.

Plan your connection

  1. Share your use case

    Describe your application, expected report volume and the actions an event should start.

  2. Agree the delivery contract

    Review the event fields, authentication, retry behaviour and data access with us.

  3. Validate before enabling

    When access is available, test duplicate events, delayed deliveries and unavailable records.

Availability and limits

Public webhooks and developer credentials are not available yet. Request this integration to discuss a custom workflow; event names and delivery details will be agreed before access is enabled.

This page describes a proposed workflow, not a current API contract. Account sessions and sign in links must never be used as credentials for an external system.

All integrations
  • Zapier

    A planned connection for routing completed reports into tasks, spreadsheets and team updates.

  • Make

    A planned connection for branching report reviews, stock updates and handovers.

  • Google Sheets

    A planned way to keep report dates and review notes beside a vehicle shortlist.