...
There are two different implementations. One uses an existing reservation through the reservation service, and the second uses subjects through the resource service.Both endpoints return
Reservation Service
The POST request in the reservation service is /api/v1/reservations/{reservationId}/reservedresources/{reservedResourceId}/addons/recommendations.
This endpoint returns a list containing add-ons and their probabilities. Both have the same It has two parameters:
size - influences the amount of recommendations that return. This defaults to 4 when left empty.
showColdStarts - When this showColdStarts = true, 25% of the request size will be random cold starts. This defaults to false.
...
Resource Service
The endpoint for the reservation POST request in the resource service is /api/v1/reservationsresources/{reservationIdresourceId}/reservedresources/{reservedResourceId}/addons/recommendationsbookableaddons/recommended.
This endpoint uses the same logic as the normal /bookableaddons endpoint, but with two optional extra parameters:
size - influences the amount of recommendations that return. This defaults to 4 when left empty.
showColdStarts - When this showColdStarts = true, 25% of the request size will be random cold starts. This defaults to false.