Vehicle Damage Detector API

Vehicle Damage Detector API

Be able to detect and estimate the damage a vehicle has. Categorize the damage and determine its severity.

API description

About the API:

With over 30 vehicle parts recognized, this API is able to provide categorizations for over 15 damage types. With advanced Machine Learning techniques, this API is trained to determine where the damage is located and its severity. 

Also, be able to get a downloadable image with the recognized damages. 

 

What this API receives and what your API provides (input/output)?

The API works with a request JSON body with these parameters. 

{
"draw_result": true,
"image": "https://i.insider.com/54da54336bb3f7156eeef89e?width=800&format=jpeg"
}

draw_result: If this flag is set to true the API will return an image with a bounding box and prediction label drawn on it (see Examples provided above). If this flag is set to false only the detection results are returned.

What are the most common uses cases of this API?

 

This API is the most used by car insurance companies that want to automatize the damage recognition of the user's cars. 

Get an idea of how bad is the damage and filter them before getting started. 

For example, a user sends the images of his car, to locate all the damages. With these pictures, you will be able to know beforehand how badly it is and have better information.  

 

Are there any limitations with your plans?

Besides API call limitations per month, there are no other limitations. 

 

Recommendations: 

  1. Try to keep the input image under 5MB, between 2000x2000 and 640x480 in resolution.
  2. To avoid longer process times we recommend not to use higher resolutions images. 
  3. For best damage detection, it's recommended to take a close picture of the area. Approx. 80cm - 1.5m when taking the picture. 

 

API Documentation

Endpoints


 

About how to use the API:

Just send an image-supported format to the API (pngjpg/jpegtiff and bmp), and  it will return the detected damagestheir coordinatesdamage types, and damaged car parts.

 

Body Parameters (JSON)

The API accepts the following payload parameters:

Key Type Default Value Value Range Required Description
image string     Yes This API accepts a publicly accessible image URL. 
remove_background boolean false true, false No  
draw_result boolean false true, false No If this flag is set to true the API will return an image with a bounding box and prediction label drew on it (see Examples provided above). If this flag is set to false only the detection results are returned.
 

Recommendations: 

  1. Try to keep the input image under 5MB, between 2000x2000 and 640x480 in resolution.
  2. To avoid longer process times we recommend not to use higher resolutions images. 
  3. For best damage detection, it's recommended to take a close picture of the area. Approx. 80cm - 1.5m when taking the picture. 
 

 



                                                                            
POST https://zylalabs.com/api/109/vehicle+damage+detector+api/163/recognize+damage
                                                                            
                                                                        

Recognize Damage - Endpoint Features
Object Description
Request Body [Required] Json
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"draw_result":true,"job_id":"52af644d-03c9-46c8-ab8c-c486fc432ade","output":{"elements":[{"bbox":[372,145,489,245],"damage_category":"slight_scratch","damage_color":[50,50,100],"damage_id":"1","damage_location":"rear_bumper","score":0.613146},{"bbox":[322,411,444,481],"damage_category":"slight_scratch","damage_color":[50,50,100],"damage_id":"1","damage_location":"rear_bumper","score":0.602163},{"bbox":[403,300,487,391],"damage_category":"slight_scratch","damage_color":[50,50,100],"damage_id":"1","damage_location":"right_rear_tire","score":0.422464},{"bbox":[404,311,491,383],"damage_category":"severe_scratch","damage_color":[0,0,120],"damage_id":"2","damage_location":"right_rear_tire","score":0.497413}]},"output_url":"https://vpai-demo-portal-shanghai.oss-accelerate.aliyuncs.com/vehicle-damage%2Fdraw-134451.7685_20220804134451.jpg?OSSAccessKeyId=LTAI5tGgUWzx5gZopTcAvNtp&Expires=1659620752&Signature=V3JNzNARJx8PvRclb1DB%2Bb4Dgw8%3D","url_expiry":"2022/08/04 13:45:52"}
                                                                                                                                                                                                                    
                                                                                                    

Recognize Damage - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/109/vehicle+damage+detector+api/163/recognize+damage' --header 'Authorization: Bearer YOUR_API_KEY' 

    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Vehicle Damage Detector API REST API, simply include your bearer token in the Authorization header.

Headers

Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.


Simple Transparent Pricing

No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.

🚀 Enterprise
Starts at $10,000/Year

  • Custom Volume
  • Dedicated account manager
  • Service-level agreement (SLA)

Customer favorite features

  • ✔︎ Only Pay for Successful Requests
  • ✔︎ Free 7-Day Trial
  • ✔︎ Multi-Language Support
  • ✔︎ One API Key, All APIs.
  • ✔︎ Intuitive Dashboard
  • ✔︎ Comprehensive Error Handling
  • ✔︎ Developer-Friendly Docs
  • ✔︎ Postman Integration
  • ✔︎ Secure HTTPS Connections
  • ✔︎ Reliable Uptime

Zyla API Hub is, in other words, an API MarketPlace. An all-in-one solution for your developing needs. You will be accessing our extended list of APIs with only your user. Also, you won't need to worry about storing API keys, only one API key for all our products is needed.

Prices are listed in USD. We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble with paying by card, just contact us at [email protected]

Sometimes depending on the bank's fraud protection settings, a bank will decline the validation charge we make when we attempt to be sure a card is valid. We recommend first contacting your bank to see if they are blocking our charges. If more help is needed, please contact [email protected] and our team will investigate further

Prices are based on a recurring monthly subscription depending on the plan selected — plus overage fees applied when a developer exceeds a plan’s quota limits. In this example, you'll see the base plan amount as well as a quota limit of API requests. Be sure to notice the overage fee because you will be charged for each additional request.

Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.

Just go to the pricing page of that API and select the plan that you want to upgrade to. You will only be charged the full amount of that plan, but you will be enjoying the features that the plan offers right away.

Yes, absolutely. If you want to cancel your plan, simply go to your account and cancel on the Billing page. Upgrades, downgrades, and cancellations are immediate.

You can contact us through our chat channel to receive immediate assistance. We are always online from 9 am to 6 pm (GMT+1). If you reach us after that time, we will be in contact when we are back. Also you can contact us via email to [email protected]

 Service Level
100%
 Response Time
3,337ms

Useful links:


Category:


Tags: