Modifying routing for a callback created via api

[Goyal_A_Aakanksha]

Hi,

We are trying to create callbacks from our website, but we don't want to have our routing logic stored in the frontend thus the website doesn't know the correct queue to schedule the callback on.
We thought of sending all the callbacks created via the website to a Generic CallBack Queue within Genesys Cloud and then make use of the In-Queue Flow to find the correct routing destination and schedule another callback on top of the first one for the correct queue.
However, we now realize that this is not an option as for the api initiated callbacks it is not touching the In Queue flows.

Does anyone have any ideas how we can enter to Genesys Cloud from our website and then do some processing in a flow and create a callback for the correct destination in that flow?

Can we maybe somehow use the "Workflow" for it ?

[tim.smith]

You have to build a middleware service that can securely handle the necessary Genesys Cloud OAuth credentials to make the authorized API requests. That might be as simple your web server's backend, or may require a separate service if your website doesn't have a programmable backend. There's an example in this project (don't mind the web chat parts, the callback and stats parts are the pattern you're interested in): https://github.com/MyPureCloud/public-stats-service.