Programmatic Web Messaging session closure failing with 404

Hey folks.

We’re trying to close a Web Messaging session from our backend service when a specific trigger happens. I found the DELETE /api/v2/webdeployments/token/revoke endpoint in the docs, but it keeps returning a 404 Not Found. The conversation ID definitely exists and is active.

Here is the curl command I’m running:

curl -X DELETE https://api.mypurecloud.com/api/v2/webdeployments/token/revoke \
 -H "Authorization: Bearer <token>" \
 -H "X-Journey-Session-Id: 12345678-1234-1234-1234-123456789012" \
 -H "X-Journey-Session-Type: webmessaging"

Is this the wrong endpoint for Web Messaging? Or do I need to use the Conversations API instead?

1 Like