Vehicle Owner Mobile Lookup API

API FOR FETCHING OWNER CONTACT FOR A GIVEN INDIAN VEHICLE REGISTRATION CERTIFICATE (RC) NUMBER

Description

Vehicle Owner Contact Information Lookup Service allows you to retrieve the owner’s contact details using just the vehicle number. By entering the vehicle number, you can access accurate and up-to-date contact information, enabling efficient verification and communication. This service is ideal for legal, administrative, insurance and customer service purposes, offering a secure and streamlined way to obtain complete ownership details while ensuring privacy and compliance with data protection regulations.

API Details

Contact lookup is available in the form of a batch upload which accepts a set of vehicle numbers as an input (excel or json array) and returns the verified details along with the registered contact number of the owner in the response.

Batch runs are asynchronous. Submitted vehicle numbers are queued and processed based on server availability. Processing may take from a few seconds to several hours, to enforce a fair usage policy. See the Webhook section below for subscribing to events and automating data capture.

STEP 1. Submit Vehicle Data API

Request

Type	URL	Current Version
POST	`https://api.attestr.com`/api/{version}/public/batchx/	v2

Request Body Parameters

Key	Type	Description	Optional (default)	Min Version
type	String	Pass value as RC_MOBILE	Required	v2
items	Array<VehicleInputObject>	List of vehicle number object for which the contact information should be fetched. See definition of Vehicle Input Object below.	Required	v2
webhook	Boolean	Whether the webhook should be called for each vehicle input. Refer to Webhooks for more details	Optional	v2

Input Vehicle Input Object

Key	Type	Description	Optional (default)	Min Version	Max Version
reg	String	Vehicle number to be verified	Required	v2

Sample Request Body

JSON
    
 
{    "type": "RC_MOBILE",    "items": [{        "reg": "MH04GF9953"    }, {        "reg": "GJ15CK0328"    }],    "webhook": false}
Copy

Request Header Parameters

Type	Name	Value / Description	Optional	Min Version	Max Version
String	Content-Type	application/json	Required	v2
String	Authorization	Basic `{authToken}`	Required	v2

If you do not have the authentication token, please refer to Register App to generate one.

Response

HTTP Status 200

Key	Description	Type	Min Version	Max Version
_id	Batch Request ID generated by the system for the set of vehicle numbers submitted.	String	v2
number	Human readable unique batch number assigned to each batch	String	v2

Sample Response

JSON
    
 
{    "_id": "BX0YgIZPVVygDTmm5P",    "number": "3957-011189-7892"}
Copy

STEP 2. Fetch Results API

Request

Type	URL	Current Version
POST	`https://api.attestr.com`/api/{version}/public/batchx/{batchId}/items	v2

Request URL Parameters

Key	Type	Description	Required/Optional
batchId	String	Batch ID generated in the previous step	Required

Request Header Parameters

Type	Name	Value / Description	Optional	Min Version	Max Version
String	Content-Type	application/json	Required	v2
String	Authorization	Basic `{authToken}`	Required	v2

Request Body Parameters

Key	Type	Description	Optional / Required	Min Version	Max Version
$skip	Number	Number of records to skip while querying the data. This key is used for pagination when a large number of vehicle registration numbers are submitted in a single batch.	Optional	v2
$limit	Number	Number of records to include in a single response. This key is used in conjunction with the "skip" key for pagination.	Optional	v2

Sample Request

Sample Request URL and Body
    
​x
 
https://api.attestr.com/api/v2/public/batchx/BX0YgIZPVVygDTmm5P/items​{  "$skip": 0,  "$limit": 100}
Copy

Response

Response Body

Key	Description	Type	Min Version	Max Version
recordsFiltered	No of records returned in the response	Number	v2
data	List of records. See Record Output Object definition below.	Array<Record Output Object>	v2

Record Output Object

Key	Description	Type	Min Version
_id	Unique ID assigned to each record in the batch	String	v2
requestId	Tracking ID used for Attestr internal purposes	String	v2
batchId	Batch ID same as generated in step one.	String	v2
number	Unique number assigned to each record in the batch	String	v2
status	Status of the request. Request can be in one of the following statuses. INITIATED, COMPLETED, ERRORED	String	v2
input	Input vehicle number submitted	Object	v2
output	Vehicle Output Data corresponding to the submitted vehicle number. See Vehicle Output Data definition below.	Object	v2

Vehicle Output Data

Key	Description	Type	Min Version	Max Version
valid	Flag indicating if the provided RC number is valid and vehicle details are fetched	Boolean	v2
status	Status of the outcome. Status can have 4 possible values. VALID_FOUND - If the details are found including mobile number NOT_FOUND - Vehicle details not available for the provided vehicle number	String	v2
contact	Mobile number of the owner if available	String	v2	-

Sample Response

Sample response for valid RC

JSON
    
 
{    "draw": 0,    "recordsTotal": 10230,    "recordsFiltered": 1,    "data": [        {            "_id": "AR0yvZcuEZGkjNk3_8",            "requestId": "daa23f8f-e5fe-4c6a-9cda-550a4da18cf3",            "batchId": "BX0g8xvUZzn0a4OLlK",            "number": "3957-195382-5764",            "status": "COMPLETED",            "input": {                "reg": "MH04GFXXXX",                "type": "RC_MOBILE"            },            "output": {                "valid": true,                "status": "VALID_FOUND",                "contact": "8890909090            },            "error": null,            "tracker": [],            "signature": "1bff17693b4de2a961ea5a2a35f2899f7ab954d7d72b124611ec15f6564d84d9",            "created": 1735973168350,            "updated": 1735974098167        }    ]}
Copy

Sample response for invalid / non existing mobile number

JSON
    
 
{    "draw": 0,    "recordsTotal": 10230,    "recordsFiltered": 1,    "data": [        {            "_id": "AR0yvZcuEZGkjNk3_8",            "requestId": "daa23f8f-e5fe-4c6a-9cda-550a4da18cf3",            "batchId": "BX0g8xvUZzn0a4OLlK",            "number": "3957-195382-5764",            "status": "COMPLETED",            "input": {                "reg": "MH04GFXXXX",                "type": "RC_MOBILE"            },            "output": {                "valid": false,                "status": "NOT_FOUND",                "contact": null,            },            "error": null,            "tracker": [],            "signature": "1bff17693b4de2a961ea5a2a35f2899f7ab954d7d72b124611ec15f6564d84d9",            "created": 1735973168350,            "updated": 1735974098167        }    ]}
Copy

Sample response if the request is in INITIATED state

JSON
    
 
{    "draw": 0,    "recordsTotal": 10230,    "recordsFiltered": 2,    "data": [        {            "_id": "AR0yvZcuEZGkjNk3_8",            "requestId": "daa23f8f-e5fe-4c6a-9cda-550a4da18cf3",            "batchId": "BX0g8xvUZzn0a4OLlK",            "number": "3957-195382-5764",            "status": "INITIATED",            "input": {                "reg": "MH04GFXXXX",                "type": "RC_MOBILE"            },            "output": null,            "error": null,            "tracker": [],            "signature": null,            "created": 1735973168350,            "updated": null        }    ]}
Copy

Error Response

Parameter	Type	Description
code	Number	Unique error codes for different errors. Always available.
message	String	Error message describing the error. Always Available.
details	String	Detail error message. Available only for certain types of errors.

Error Codes

HTTP Status	Error Code	Error Message
400	4001	Malformed data or missing required parameter values
400	4005	Operation could not be performed due to low credits balance
401	4016	Invalid client authorization
403	4031	Unauthorized access
403	4035	Requested service is not provisioned for your account
403	4039	Client's IP address is not whitelisted
403	4035	Requested service is not provisioned for your account
429	4291	Maximum account rate limit exceeded
429	4292	Maximum API rate limit exceeded
429	4293	Maximum account daily limit exceeded
429	4294	Maximum API daily limit exceeded
500	5001	Request could not be processed

Sample Error Response

JSON
    
 
{  "code": 4001,  "message": "Malformed data or missing required parameter values"}
Copy

Webhooks

Vehicle Owner Contact Lookup API supports the following two webhook events.

See Webhooks for more details on how to register webhooks.

async.completed
async.errored

To enable webhooks, the API input parameter webhook must be set as true while initiating the request.

Webhook Event Payload

Key	Type	Description	Min Version
_id	String	ID of the async request. This is same as received in the output of Person / Business search API as described above.	v1
requestId	String	Unique request ID for internal tracing purposes.	v1
status	String	One of COMPLETED OR ERRORED	v1
output	Object	Record Output Object same as described above	v1
error	Object	Error object if the request ran into errors. The structure of this is same as the Error Response object described above.	v1
signature	String	generated using hmacHexDigest of output object and client secret. Null if status is errored.	v1

Validating the signature

Generate signature on your server side code base and check if it matches the signature returned in the payload. To generate the signature, use the SHA256 algorithm, the client secret and the output value to generate a HMAC Hex Digest as shown in the sample code below.

Node.js
Java
    
 
const crypto = require("crypto");​var clientSecret; // This should be initialized as client secret.var apiResponse; // This is apiResponse as retuned in step 6.​function hmacHexDigest(secret, input) {    const hmac = crypto.createHmac('sha256', secret)    hmac.update(input)    return hmac.digest('hex')}​var signature = hmacHexDigest(clientSecret, JSON.stringify(eventPayload.output));​// Check if signature matchesif(signature !== apiResponse.resultSignature){  // Flow is tampered.}
Copy

Last updated on

vehicle owner contact lookupvehicle to mobile numberrc to mobile numbervehicle owner mobile