Authentication is performed using OAuth 2.0 Bearer Token.
Interface Mapping
The search interface for search and detail queries must return the following fields per vehicle. For the search, at least vehicleNo must be populated, which is used at Belbo as an internal key between the DMS and belbo:
| Attribute | Type | Description |
|---|---|---|
letterSalutation | String | Salutation for letters, e.g. "Dear". |
salutationCode | String | Code for the salutation, e.g. "MR" or "MRS". |
customerNo | String | Unique customer number. |
firstname | String | Customer's first name. |
lastname | String | Customer's last name. |
phoneNumber | String | Customer's phone number. |
email | String | Customer's email address. |
company | String | Name of the company, if applicable. |
city | String | Customer's city or town of residence. |
postalCode | String | Customer's postal code. |
street | String | Customer's street and house number. |
lastServiceText | String | Description of the last service event. |
licensePlate | String | Vehicle registration number. |
category | String | Vehicle category, e.g. "car" or "truck". |
mileage | Integer | Current vehicle mileage. |
nextEmissionCheck | Date | Date of the next emission test. |
vehicleMake | String | Vehicle make, e.g. "BMW". |
vehicleModel | String | Vehicle model, e.g. "3 Series". |
vehicleNo | String | Vehicle registration number. |
vin | String | Vehicle Identification Number (VIN). |
serialNumber | String | Serial number of the vehicle or a related component. |