Tint API
Validation Schema
In the previous section How Tint Works, we have seen how your platform has to send data to underwrite policies (and quotes) via the Tint REST API and how our API can be customized to match your data model.
This is done thanks to a validation schema, which defines:
  1. 1.
    The policy's underwriting information structure your platform will send as payload to the Tint API;
  2. 2.
    The potential inputs used by the different models configured on the Tint application.
External data providers can also be used on top of your platform data to underwrite policies, such as credit score checks, motors vehicle records, digital identity check...
The validation schema is the keystone of your insurance product. It puts your use case and data at the heart of our system.
In the car rental platform example, the validation schema JSON object sent to the Tint API could look something like this:
"vehicle": {
"id": "your car ID here",
"value": 10000,
"make": "BMW",
"model": "325i",
"year": 2019
"reservation": {
"id": "your reservation ID here",
"startDate": "2022-05-25",
"endDate": "2022-05-29",
"bookedAt": "2022=05-20"
"renter": {
"id": "your renter ID here",
"drivingLicence": "1234ABCD",
"birthDate": "1988-10-14",
"firstName": "John",
"lastName": "Doe"
Once you have configured your validation schema, you can move on to the configuration of your insurance product.
Copy link