Skip to main content

Hello Community,

Our team is exploring the FSM OOTB Rest API perform_threesixty_appt_offer_accept in order to use it to accept a slot after getting slots using the FSM OOTB Rest API perform_threesixty_appt. 

From what we could understand, on the cases that we are accepting a slot that the system consider not available - meaning that availability is equal to False - the system retrieves the error "The requested appointment is no longer available. Please restart appointment booking process.".

However, for example, if we try to accept a slot that is no longer available due to a new unavailability of the resource or another allocation for the same slot or the slot to be picked by another agent should we expect the same response? From our tests, we could not confirm with 100% sure these described scenarios and the related Rest API responses.

 

Thank you so much!

Joana Machado

I would try it through the FSM Web Client or Smart Client and look at the JSON or XML log to see how the FSM Client is managing the appointment booking MPM calls.  If you’re using the FSM Web Client, Fiddler is your friend.  ;-)

Terms & ConditionsCookie settings