Virtual Services are non-located services. They can be used to display partner managed custom services at the end of the Check flow.
The basic structure includes all possible Virtual Service properties, that is refined by Virtual Service sub-types. The exact sub-types define the accessible properties by Virtual Service type. This structure can represent all of them with optional properties.
Structure
|
Property name |
Property type |
Property description |
|---|---|---|
|
|
string |
ID of the service |
|
|
string |
Name of the Service |
|
|
string |
Description of the Service |
|
|
Type of the Virtual Service |
|
|
|
Gender of the service, where available |
|
|
|
string? |
Telephone number, null if does not exist |
|
|
string? |
E-mail of the Service, null if does not exist |
|
|
string? |
URL of the service, where available |
|
|
|
Array of service specializations See GET /v1/services/features/:countryCode endpoint about available properties. |
|
|
string[]? |
Optional IDs of service’s supported insurers |
|
|
Opening hours, for each day of the week, in format of arrays of open sections Day 0 means Monday See GET /v1/services/features/:countryCode endpoint about available properties. |
|
|
|
string |
Monogram of the Service |
|
|
string? |
Publicly available profile photo / logo of the service |
See sub-types: