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

Deceased Check

Powered by Sagacity

Marketing to the deceased is brand damaging, a waste of marketing spend and will impact on campaign performance.

Since its inception in 2000, The Bereavement Register (TBR) has built a reputation for providing a high quality, reliable file of confirmed deceased records. Data is collected directly from the bereaved and/or third party sources of actual deaths with no assumed data included.

 

This service is the most efficient, accurate and cost effective way to ensure customers who have passed away are removed from your marketing campaigns.  

 

Pay-on-results* pricing allows you to check prior to each contact with your customers, minimising cost whilst achieving the highest level of protection for your brand.

 

Key features:

 

  • Utilises the Bereavement Register

  • Cross referenced against multiple third-party datasets to deliver an accurate and comprehensive service

  • Pay-on-results pricing*

  • From 70p per result

*Pay-on-results mean you only pay for checks where a deceased record is found.

 

Pricing

PAYG
£1.50
Per Use
Business
£1.00
Per Use
Enterprise
70p
Per Use

Pricing

PlanGBPEURUSD
PAYG (Per Use)£1.50€1.80$2.10
Business (Per Use)£1.00€1.20$1.40
Enterprise (Per Use)70p84c98c

Sample Response

Documentation

Introduction

This endpoint identifies where a deceased record has been found.

Header

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

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

Example Request

https://api.oneautoapi.com/sagacity/deceased?full_name=Jane Smith&address_1=1a First Avenue&address_2=Example Address Line 2&address_3=Example Address Line 3&address_4=Example Address Line 4&address_5=Example Address Line 5&address_6=Example Address Line 6&address_7=Example Address Line 7&unique_reference=123&date_of_birth=1942-07-07

Example Sandbox Request

https://sandbox.oneautoapi.com/sagacity/deceased?full_name=Jane Smith&address_1=1a First Avenue&address_2=Example Address Line 2&address_3=Example Address Line 3&address_4=Example Address Line 4&address_5=Example Address Line 5&address_6=Example Address Line 6&address_7=Example Address Line 7&unique_reference=123&date_of_birth=1942-07-07

Request Parameters

full_name
mandatory, string, e.g. Jane Smith
The customer's full name
address_1
mandatory, string, e.g. 1a First Avenue
The first line of the customer's address
address_2
mandatory, string, e.g. Example Address Line 2
The second line of the address
address_3
optional, string, e.g. Example Address Line 3
The third line of the address
address_4
optional, string, e.g. Example Address Line 4
The fourth line of the address
address_5
optional, string, e.g. Example Address Line 5
The fifth line of the address
address_6
optional, string, e.g. Example Address Line 6
The sixth line of the address
address_7
optional, string, e.g. Example Address Line 7
The seventh line of the address
unique_reference
optional, string, e.g. 123
The unique reference number associated to the supplied name and address
date_of_birth
optional, string, e.g. 1942-07-07
The person's date of birth

Sample Response

{
  "success": true,
  "result": {
    "is_deceased": true,
    "unique_reference": "Your reference",
    "source": "Example Source"
  },
  "error": "If there is an error the message would go here"
}

Response Parameters

success
e.g. true
Whether the api call was successful
is_deceased
e.g. true
Is the person deceased
unique_reference
e.g. Your reference
The unique reference number associated to the supplied name and address
source
e.g. Example Source
The source of the data
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 Sagacity