Requested Change: Please include a service_addons array in the JSON POST payload.
We are requesting a important update for us to the External Booking Validator payload to support complex business logic.
-
Currently, we use the validator for our beauty-at-home service to verify geographic coverage and it works like a charm as we have the provider id and the user id, but we are blocked from implementing a necessary service compatibility matrix. Our protocol allows multiple paid add-ons and also free add-on used as service variant (extras performed during the 45-60 min pause time of the main service). For example, for a bio coloration, during 45 min the product needs to process; we want the customer to be able to select a manucure, pedicure OR face treatment. Our matrix is too complex to implement proper options in the custom feature, we will guide the client to select one of the three options/variants. We can survive if the client select multiple one if we can block it during he booking confirmation.
-
The Limitation: The validator sends the
service_id, but lacks theservice_addonsselected by the client. Without these IDs, we cannot programmatically verify if the booking scope complies with our operational policies or if the provider is fully qualified for the extras selected.
Find below our happy payload 
{ “category_id”: “1”, “location_id”: “1”, “company_login”: “*****************”, “additional_fields”: [], “count”: “1”, “client_id”: “1”, “start_datetime”: “2026-02-22 14:30:00”, “provider_id”: “2”, “service_id”: “2”, “service_addons”: [“15”, “22”] }
We hope that it could be a quick win to implement as we are actually stuck with that.
