I would recommend NOT going again to the CDN to retrieve the config. This should be considered an internal data structure by Genesys and could be subject to a breaking change with notification to only one. A better approach would be to call GET /api/v2/webdeployments/deployments/{deploymentId} and then get the configuration id out of the returned Configuration attribute. From there you should be able to call GET /api/v2/webdeployments/configurations/{configurationId}/versions and filter out the version that is Active. Our APIS are versioned and we enforce a well-defined breaking change policy on our APIs.
I hope that helps.
Thanks,
John Carnell
Director, Developer Engagement
One of my co-workers pointed out that you can't use the endpoints here because you are building a guest interface and need to be authorized. I would still recommend that you do not go against the CDN because that is not a version interface. I am going to forward your situation to the Web messaging team and see if they have any advice.
Thanks,
John Carnell
Director, Developer Engagement
I also tried /api/v2/webdeployments/deployments/{deploymentId}/configurations with the guest JWT token and I got 401. I guess these calls need an agent authorization.
You got 401 because you weren't authenticated. The web messaging guest api is inteneded for guest chats. We deployed a chat using the WMGA, which requires validation of aditional information from Genesys Apis, so, we deployed an api backend to talk with Genesys endpoints B2B.