Quick Assess — Inspect, Assess, Verify

Quick Assess API V2

Use an opaque vehicle reference safely.

Make/model/variant values must match the active Quick Assess catalogue. Clients cannot create arbitrary catalogue records or select an insurer ID.

Start integration API reference

Workflow

  • POST /api/v2/vehicles with make, model, manufacture_year and at least one identity reference.
  • Store the returned opaque vehicle_reference; do not treat it as a registration or database ID.
  • Reuse the same Idempotency-Key after an uncertain network response.
  • Use GET for safe detail or list projections and PATCH with the current integer version for approved updates.
  • Use GET /assessments for safe history references only.

Synthetic request

{
  "external_vehicle_reference": "SYNTHETIC-VEHICLE-001",
  "make": "MERCEDES BENZ",
  "model": "C CLASS- W202",
  "manufacture_year": 2001,
  "registration_number": "UAA 123X",
  "chassis_number": "SYNTHETIC-CHASSIS-001"
}

Identity and isolation

external_vehicle_reference is your system reference. vehicle_reference is the stable opaque Quick Assess reference. Registration, chassis and external references are normalized and matched only within the authenticated insurer. Conflicts return 422 vehicle_identity_conflict; records are never silently merged.

Need access or integration support?

Integration supportContact Quick Assess