This service makes it easy to check for a change of keeper prior to every communication, protecting your reputation and ensuring you comply with GDPR.
Pay-on-results* pricing allows you to minimise cost while achieving better protection than periodic data cleanses.
*only pay for checks that identify a keeper change since the last seen date
Key Features
VRM-based Lookup
Easily identify keeper changes by registration mark
Last Seen Date
Check whether a change of keeper has occurred since your last contact
Pay on Results Pricing
Only pay where a change of keeper is identified
Improves Customer Contact
Improve the quality of your customer contact by ensuring the correct context is applied
Increases Your Compliance
Ensure a higher level of compliance with GDPR by checking in real-time prior to each contact
Maximise Response Rates
Improve the response rate of outbound campaigns by ensuring communications are relevant and compliant
Sample Response
V2
Documentation
Introduction
This endpoint identifies where a keeper change has occurred since a given date, returning UK Vehicle Data's key vehicle and basic provenance data.
Header
When making calls to our API, include the following header:
x-api-key:your-api-key-here
Example Request
https://api.oneautoapi.com/ukvehicledata/keeperchangefromvrm?vehicle_registration_mark=AB21ABC&last_seen_date=2018-01-01
Example Sandbox Request
https://sandbox.oneautoapi.com/ukvehicledata/keeperchangefromvrm?vehicle_registration_mark=AB21ABC&last_seen_date=2018-01-01
Request Parameters
vehicle_registration_mark
mandatory, string, e.g. AB21ABC
Vehicle registration number
last_seen_date
mandatory, string, e.g. 2018-01-01
The date from which you would like to complete the check from
Sample Response
{
"success": true,
"result": {
"keeper_change": true,
"date_of_last_keeper_change": "2020-01-01"
},
"error": "If there is an error the message would go here"
}Response Parameters
success
e.g. true
Whether the api call was successful
keeper_change
e.g. true
The has had a keeper change.
date_of_last_keeper_change
e.g. 2020-01-01
The date of last keeper change.
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