When using the Chaiz API access, it is your responsibility to implement the UI that users interact with to ensure they properly understand the product they are purchasing.
As VSCs face significant regulatory scrutiny, a delicate balance must be struck between sales optimisation and compliance. Moreover, owing to the presence of various bad actors in the industry and increased consumer awareness, users are less receptive to tactics employed in other e-sales funnels.
Below, we shall examine each API call along with its response, detailing which fields must be displayed and how chaiz.com should be represented.
<aside> 👉
Please remember that Chaiz must formally approve your implementation before it can go live. Failing to obtain this approval may result in the revocation of your partner access token. Additionally, Chaiz reserves the right to request access to the implementation from time to time to verify the accurate representation of Chaiz and its providers.
</aside>
When calling /PlanSearch or /PlanSearchAsync, you receive a set of vehicle service contract options that fit the vehicle's make/model, year, mileage, and state. You then present the information to your users.


providerDisplayName can be used, but Chaiz must approve the overall design.planName . To be shown as this is the primary differentiating orientation point for users following to the pricecoverageTypeId see API desc for mapping. Indicate the coverage level of a plan.duration and miles so that the customer understands how long the coverage lasts. It is either or, which ever comes earlier, and miles are added to the current odometer.Optional Fields (blue)
categories lists categories that have covered items under this plan. Be aware this can also mean that just one item within this category is covered.rating on chaiz.com is a compilation of social ratings, our own experience with the provider, and customer feedback.