UAE Accident History

Overview and Purpose

Overview

The UAE Accident History API is an advanced, comprehensive resource designed to deliver extensive information on the accident history of vehicles registered within the United Arab Emirates. By leveraging the unique chassis number of a vehicle as a query parameter, this API offers unparalleled access to a detailed history of accidents associated with the vehicle. This tool is invaluable for users seeking in-depth data on a vehicle's safety and operational history within the UAE.

Key Features

Chassis Number Identification: Utilizing the vehicle's chassis number as a key identifier, the Dubai Accident History API offers broad coverage across nearly all vehicles registered in the UAE. This feature ensures that the API can cater to a wide array of requests, providing accurate and specific accident history data.
Comprehensive Accident Details: The API furnishes users with detailed information regarding a vehicle's accident history. This includes, but is not limited to, the date, time, and location of each accident, alongside insights into the causes and the specific parts of the vehicle that were damaged. Such detailed records are crucial for understanding the extent and nature of accidents a vehicle has been involved in.
Accident Imagery: In addition to textual data, the API also provides access to photographs depicting the vehicle post-accident. These images, captured from various angles, offer a visual understanding of the damage incurred, enhancing the overall comprehensiveness of the accident history report.

This API serves as a critical tool for individuals and organizations aiming to make informed decisions regarding vehicle safety, maintenance, and history in the UAE. Its ability to provide detailed accident reports, including photographic evidence, makes it an indispensable resource for assessing vehicle integrity and history.

Use Cases

Pre-Purchase Inspection for Buyers - Potential vehicle buyers can utilize the Dubai Accident History API to conduct a thorough pre-purchase inspection. By entering the chassis number, buyers can access a detailed accident history, including past damages and repairs, to make an informed decision before finalizing their purchase. This transparency ensures that buyers are fully aware of the vehicle's condition and history.
Insurance Claim Processing and Policy Issuance - Insurance companies can leverage the API to streamline their claim processing and policy issuance workflows. Access to detailed accident histories allows insurers to accurately assess a vehicle's risk profile, facilitating informed decision-making regarding claim settlements and premium calculations. The API's provision of accident photos further aids in verifying claims and understanding the extent of damages.
Traffic Regulation and Legal Compliance - Traffic and legal authorities can employ the Dubai Accident History API to enhance their monitoring and regulatory efforts. By accessing comprehensive accident records, authorities can ensure vehicles meet safety standards and comply with UAE traffic laws. The API aids in identifying vehicles with a history of frequent accidents or significant damages, contributing to road safety initiatives.
Vehicle Maintenance and Ownership Records - Vehicle owners benefit from the API by being able to check their vehicle's accident history and related details, ensuring they are informed about any past incidents that may affect their vehicle's performance and value. This feature is crucial for maintaining transparency in vehicle ownership and for owners aiming to maintain or sell their vehicles.
Market Research in the Automotive Sector - The API serves as a valuable resource for market researchers and analysts focusing on the automotive industry in Dubai. By providing access to accident history data across various vehicle models and years, the API enables detailed trend analysis, market predictions, and insights into the safety records of different vehicles, informing industry strategies and consumer advisories.
Service Center Verifications - Maintenance and service centers can use the Dubai Accident History API to verify a vehicle's history before undertaking repairs or maintenance work. This pre-service check ensures that service professionals are aware of any previous damages that might affect current repairs, providing a basis for accurate service recommendations and safety certifications.

Coverage :- Ministry of Interior, UAE

API Details

The UAE Accident History API is designed to provide users with comprehensive accident history reports for vehicles registered in the United Arab Emirates. Here is a detailed overview of the API's input and output specifications:

Input Parameters : Users must provide the chassis number of the vehicle they wish to inquire about. This number enables the API to accurately retrieve all relevant accident data associated with the specific vehicle.

Output Data:

Accident Details: For each accident associated with the vehicle, the API returns a detailed report that includes:
- Date and Time: The exact date and time when the accident occurred.
- Location: The geographical location where the accident took place.
- Causes of the Accident: An analysis or description of what caused the accident, based on available data.
- Damaged Parts: A list of vehicle parts that were damaged in the accident, providing insight into the extent and nature of the damage.
Photos of the Accident: The API provides photographs of the vehicle post-accident, taken from various angles. These images help to visually assess the damage and validate the accident details.
Number of Accidents: A count of the total number of accidents recorded for the vehicle, giving users an immediate sense of the vehicle's accident history.

Since this is an Async API, The response will be received on webhook, If one dont have a webhook they can use a get request to get the data

This structured approach allows for a comprehensive understanding of a vehicle's accident history, assisting various stakeholders in making informed decisions regarding vehicle purchase, insurance, maintenance, and regulatory compliance.

Sample Request cURL

curl --location 'https://api-preproduction.signzy.app/api/v3/uae/vehicle-accident-history' \
--header 'Content-Type: application/json' \
--header 'Authorization: <Auth Token>' \
--data '{
    "chassisNumber": "<chassis number>",
    "callbackUrl": "https://webhook.site/a61356ae-eb02-4e19-9d78-762f5b04445e"
}'

Request Body Parameters

Parameter	Data Type	Description
chassisNumber	String	chassis number of vehicle, 17 digit alphanumeric sequence
callbackUrl	String	The callback URL/Webhook where response will be received

Sample Response POST Request

When the initial request is made, in it's response, user will receive a request ID, the request ID can be used in the request body of GET API. This will help fetch the corrosponding data

{
    "result": {
        "requestId": "66055524e19c128487661a14",
        "statusCode": 200,
        "status": "SUCCESS"
    }
}

GET Request Sample cURL

// Get Data for Request ID
curl --location 'https://api-preproduction.signzy.app/api/v3/uae/vehicle-accident-history-get-data' \
--header 'Content-Type: application/json' \
--header 'Authorization: <AUTH TOKEN>' \
--data '{
    "requestId": "6602c5c031f89fb2fe071566"
}'

Sample Response Success (Callback URL/GET Data Request)

{
  "requestId": "6602c5c031f89fb2fe071566",
  "input": {
    "chassisNumber": "KNMCC42H89P724182",
    "callbackUrl": "https://webhook.site/a61356ae-eb02-4e19-9d78-762f5b04445e"
  },
  "statusCode": 200,
  "status": "SUCCESS",
  "message": "UAE vehicle accident history details found",
  "output": {
    "totalNumberOfAccidents": "5",
    "accidents": [
      {
        "reportNumber": "550071244775",
        "reportType": "Accident without injuries",
        "reportDate": "30/12/2017",
        "time": "23:24",
        "accidentType": "SIDE COLLISION",
        "crossingStreet": "Sheikh Maktoum Bin Rashid Street",
        "distanceFromIntersection": "0",
        "light": "NA",
        "locationType": "NA",
        "emirate": "Sharjah",
        "year": "2017",
        "serviceCentre": "SAAED - SHARJAH",
        "speedLimit": "60 Km/Hour",
        "street": "Sharjah-Sharjah City-Al Meraigah-Al Hosun Street",
        "streetCondition": "NA",
        "nearTo": "NA",
        "accidentCauses": [
          "Not giving way or priority"
        ],
        "damagedParts": [],
        "photos": [
          "https://persist.signzy.tech/api/files/868748313/download/a9271bc6201547f1873f982f20bf3f9bd7867801c23c49b3ba1657ccbca028d7.png",
          "https://persist.signzy.tech/api/files/868748319/download/14d2d1aac6944eb18d644522f62e6a28ce5c9bd2d61c4bf7b0eaf6a78b091daa.png",
          "https://persist.signzy.tech/api/files/868748323/download/14baa9167dd24232865bd8c0df537a6cf6a20cac5f0e48c78268871679eefd84.png"
        ]
      },
      {
        "reportNumber": "387673",
        "reportType": "Accident without injuries",
        "reportDate": "22/08/2012",
        "time": "05:00",
        "accidentType": "SIDE COLLISION",
        "crossingStreet": "",
        "distanceFromIntersection": "0",
        "light": "NA",
        "locationType": "NA",
        "emirate": "Sharjah",
        "year": "2012",
        "serviceCentre": "Sharjah Traffic Department",
        "speedLimit": "80 Km/Hour",
        "street": "Sharjah-Sharjah City-Al Abar-Saleh Bin Muslim Street",
        "streetCondition": "NA",
        "nearTo": "NA",
        "accidentCauses": [
          "Not driving within road limits"
        ],
        "damagedParts": [
          "REAR RIGHT SIDE"
        ],
        "photos": []
      },
      {
        "reportNumber": "550061076014",
        "reportType": "Accident without injuries",
        "reportDate": "02/08/2016",
        "time": "17:04",
        "accidentType": "REAR-END COLLISION",
        "crossingStreet": "Sheikh Maktoum Bin Rashid Street",
        "distanceFromIntersection": "0",
        "light": "NA",
        "locationType": "NA",
        "emirate": "Sharjah",
        "year": "2016",
        "serviceCentre": "SAAED - SHARJAH",
        "speedLimit": "20 Km/Hour",
        "street": "Sharjah-Sharjah City-Al Mahattah-Musab Bin Omair Street",
        "streetCondition": "NA",
        "nearTo": "NA",
        "accidentCauses": [
          "Reversing without checking if road is empty"
        ],
        "damagedParts": [
          "OTHERS (SPECIFY)",
          "FRONT RIGHT ANGLE",
          "FRONT RIGHT SIDE"
        ],
        "photos": []
      },
      {
        "reportNumber": "141091027593",
        "reportType": "Accident without injuries",
        "reportDate": "12/07/2009",
        "time": "21:11",
        "accidentType": "SIDE COLLISION",
        "crossingStreet": "Truck Road (Abu Dhabi - Al Ain)",
        "distanceFromIntersection": "0",
        "light": "NA",
        "locationType": "NA",
        "emirate": "Abu Dhabi",
        "year": "2009",
        "serviceCentre": "SAAED FOR TRAFFIC SYSTEM",
        "speedLimit": "60 Km/Hour",
        "street": "Abu Dhabi-Mussafah Industrial Area----Mussafah Road",
        "streetCondition": "NA",
        "nearTo": "NA",
        "accidentCauses": [
          "Not driving within road limits"
        ],
        "damagedParts": [
          "REAR RIGHT SIDE"
        ],
        "photos": []
      },
      {
        "reportNumber": "550051015981",
        "reportType": "Accident without injuries",
        "reportDate": "20/02/2015",
        "time": "13:21",
        "accidentType": "ONROAD COLLIDE W. FIXED OBJECT",
        "crossingStreet": "Western Border Checkpoint",
        "distanceFromIntersection": "0",
        "light": "NA",
        "locationType": "NA",
        "emirate": "Sharjah",
        "year": "2015",
        "serviceCentre": "SAAED - SHARJAH",
        "speedLimit": "60 Km/Hour",
        "street": "Sharjah-Sharjah City-Al Nad-King Faisal Street",
        "streetCondition": "NA",
        "nearTo": "NA",
        "accidentCauses": [
          "Neglect and inattention"
        ],
        "damagedParts": [
          "FRONT RIGHT ANGLE",
          "FRONT LEFT ANGLE",
          "VEHICLE FRONT",
          "VEHICLE FLOOR",
          "MORE THAN THREE PARTS",
          "OTHERS (SPECIFY)"
        ],
        "photos": []
      }
    ]
  }
}

Response Body Parameters

Field Name	Data Type	Description
totalNumberOfAccidents	String	The total number of accidents recorded for the vehicle.
accidents	Array	A list of accident records.
reportNumber	String	Unique identifier for the accident report.
reportType	String	Type of report filed (e.g., Accident without injuries).
reportDate	String	Date when the accident report was filed.
time	String	Time when the accident occurred.
accidentType	String	Type of accident (e.g., REAR-END COLLISION, SIDE COLLISION).
crossingStreet	String	Name of the crossing street at the accident location.
distanceFromIntersection	String	Distance from the nearest intersection at the time of the accident.
light	String	Lighting condition at the accident scene (e.g., UNKNOWN).
locationType	String	Type of location where the accident occurred (e.g., UNKNOWN).
emirate	String	The emirate where the accident occurred.
year	String	Year when the accident occurred.
serviceCentre	String	Name of the service centre that reported the accident.
speedLimit	String	Speed limit in the area where the accident occurred.
street	String	Street name or location of the accident.
streetCondition	String	Condition of the street at the time of the accident (e.g., UNKNOWN).
nearTo	String	Notable location or landmark near the accident scene (e.g., UNKNOWN).
accidentCauses	Array of Strings	List of causes attributed to the accident.
damagedParts	Array of Strings	List of vehicle parts that were damaged in the accident.
photos	Array	A collection of photo URLs or paths related to the accident (empty if no photos are available).

Error code Responses

{
    "error": {
        "name": "error",
        "message": "Internal Server Error",
        "reason": "INTERNAL_SERVER_ERROR",
        "type": "Internal Server Error",
        "statusCode": "500"
    }
}

Error Response Parameters

Parameter	Description
error	This parameter contains the error
name	The name of the error
message	The error message
statusCode	HTTP Status Code of the request
reason	Reason for error
type	Type of the error
status	Status code from Signzy

Getting help

Please feel free to contact us if you have any questions, require clarification, or have ideas for how to make the documents or any of our services better.

You can reach out to us at [email protected]. We strive to provide prompt and reliable assistance, ensuring your queries are addressed effectively.

We value your feedback and are committed to making your experience smooth and enjoyable. Our team is dedicated to assisting you with any needs you may have. Thank you for choosing our services. We look forward to helping you!