UK-EN
Home|API|Vehicle Check App|Bulk Vehicle Reports|Consultancy|Pricing|Knowledge Base|Swagger|Blog|Contact Us

Salvage Check from VRM

Powered by SalvageGuide

3M+ UK Records with Damage Data & Image Links

Extra protection for all buyers of used vehicles.

Each year hundreds of thousands of vehicles are sold through salvage auction,  many with serious damage or mechanical issues - often finding their way back into the market with hidden defects.  

Checking for salvage history provides additional reassurance for consumers,  and is a valuable tool for the retail motor trade when buying stock.  Also of value to insurers, warrantly providers and lenders in assessing risk for new policies and agreements.

Key Features

3m+ Salvage Records

The largest salvage database in the UK offering comprehensive coverage

Damage Descriptions

Identify the condition of the vehicle when sold at salvage auction

Salvage Image Links

Links to 3rd party websites showing images (where available)

Lot ID and Description

Identifies the auction lot ID to enable cross-verification with other data

Mileage

The odometer reading at the date of sale

Date of Sale

Identifies when the vehicle was sold for salvage

Pricing

PAYG
50p
Per Use
Business
20p
Per Use
Enterprise
10p
Per Use

Pricing

PlanGBPEURUSD
PAYG (Per Use)50p60c70c
Business (Per Use)20p15c29c
Enterprise (Per Use)10p12c15c

Sample Response

Documentation

Introduction

This endpoint identifies vehicles that have previously been listed for sale in a salvage auction. Salvage records include the lot date, description, mileage and damage details.

Header

When making calls to our API, include the following header:

x-api-key:your-api-key-here

Example Request

https://api.oneautoapi.com/carguide/salvagecheck?vehicle_registration_mark=AB21ABC

Example Sandbox Request

https://sandbox.oneautoapi.com/carguide/salvagecheck?vehicle_registration_mark=AB21ABC

Request Parameters

vehicle_registration_mark
mandatory, string, e.g. AB21ABC
Vehicle registration number

Sample Response

{
  "success": true,
  "result": {
    "salvage_auction_record_found": true,
    "salvage_auction_records": [
      {
        "salvage_auction_record_id": 1234567,
        "salvage_auction_lot_desc": "CAT S - Repairable Structural",
        "salvage_auction_lot_date": "2020-01-01",
        "mileage": 12345,
        "primary_damage_desc": "Slight Front Damage",
        "secondary_damage_desc": "Unable to select 5th gear, steering poor.",
        "salvage_auction_location": "York",
        "external_image_urls": [
          "https://images.examplewebsite.com/salvageimages12a34b5/1234AB5C_hrs.jpg"
        ]
      }
    ]
  },
  "error": "If there is an error the message would go here"
}

Response Parameters

success
e.g. true
Whether the api call was successful
salvage_auction_record_found
e.g. true
Salvage record has been found
salvage_auction_record_id
e.g. 1234567
Salvage record id
salvage_auction_lot_desc
e.g. CAT S - Repairable Structural
Salvage auction lot description
salvage_auction_lot_date
e.g. 2020-01-01
The salvage auction date
mileage
e.g. 12345
The current mileage of the vehicle in full
primary_damage_desc
e.g. Slight Front Damage
The primary damage description
secondary_damage_desc
e.g. Unable to select 5th gear, steering poor.
The secondary damage description
salvage_auction_location
e.g. York
Salvage auction's location
error
e.g. If there is an error the message would go here
Details of what went wrong with the api call

Status Codes

200
success, chargeable
Request has been successfully received and a response has been sent.
202
accepted, non-chargeable
Request has been received and accepted for processing, but the action has not yet been completed.
204
no content, non-chargeable
Request has been successfully received but there is no content to return e.g. if an invalid VRM has been sent.
206
partial content, non-chargeable
Request has been successfully received but limited content is returned e.g. if an invalid VRM has been sent.
400
bad request, non-chargeable
Request was not received e.g. if any required parameters are missing.
403
forbidden, non-chargeable
Request was rejected e.g. if the API key is invalid or the service is not enabled.
429
too many requests, non-chargeable
API key rate limit/quota has been exceeded.
500
internal server error, non-chargeable
We are unable to process the request e.g. if the API is under extremely heavy load.
503
service unavailable, non-chargeable
Service is temporarily unavailable. Contact help@oneautoapi.com

Also Available From SalvageGuide