Skip to main content
Solved

Live Agent Handoff - Webhook Token for Glia - LIVE_AGENT_UNABLE_TO_START_CONVERSATION

  • February 25, 2026
  • 11 replies
  • 69 views

Hi all,

 

We have our prod environment set up with Moveworks configured to have a Live Agent Handoff with Glia. We want to make sure our Sandbox is configured properly too.

 

We have a site ID that we inputted as well as a queue ID, but we’re unsure of what our Webhook Token should be - if it’s generated already, how to generate it if it isn’t, or how to retrieve it if it already exists. Do we need to setup/configure a connector?

 

Right now when a live agent handoff attempt is made in our Sandbox environment, the live agent interaction/request is not seen on Glia’s agent side so it seems that it is not reaching Glia at all, and the response on our Moveworks bot is “I attempted again to start a live agent chat for you using the description you provided; the request first went into a pending state and then failed with the internal error LIVE_AGENT_UNABLE_TO_START_CONVERSATION, meaning the system was unable to open a conversation with a live agent.”

Does anyone have thoughts on how we can resolve this?

Best answer by varockiasamy

Hi,

 

The webhook token will be the Moveowrks API key. You can generate the API key following this document.

11 replies

varockiasamy
  • Employee
  • Answer
  • February 25, 2026

Hi,

 

The webhook token will be the Moveowrks API key. You can generate the API key following this document.


  • Author
  • Participating Frequently
  • February 25, 2026

Hi all, I think I have the correct webhook token now, but I am getting the following response:

I attempted again to start a live agent chat for you with the description you provided, but the request failed due to an internal system error with the target URL (https:///visitors?")`), so the conversation with a live agent could not be opened.

How/where change I alter the target URL?


varockiasamy
  • Employee
  • February 25, 2026

Hi,

 

It looks like you have the wrong connector selected in Handoff → Live Agent Handoff. Kindly change it to the one that you recently created and try again.


  • Author
  • Participating Frequently
  • February 25, 2026

Hi, I reverted to that one and got the same result, so then I tried changing the api key id for that connector (as I’m not actually sure which api key ID to use for the connector) as well and I’m still not able to successfully accomplish the live agent handoff


varockiasamy
  • Employee
  • February 25, 2026

I think we are failing to generate the token. It might be that the credentials in the connector are not valid. Can you run this cURL request with the ID and secret that you have in the connector ?

 curl -X POST https://api.glia.com/sites/tokens \
-H "Content-Type: application/json" \
-H "Accept: application/vnd.salemove.v1+json" \
-d '{"api_key_id":"<your_id>","api_key_secret":"<your_secret>"}'

 


  • Author
  • Participating Frequently
  • February 26, 2026

I honestly am not sure which is the correct api key id and which is the correct api key secret. So I’d like to generate new ones entirely instead of trying to find out what the previous ones were. What would be the best way to do that?


  • Author
  • Participating Frequently
  • February 26, 2026

Nevermind, I just generated a new client ID and secret and inputted it into the connector, will try to test out now


  • Author
  • Participating Frequently
  • February 26, 2026

Ok, here are the steps i took:

-generated a new client ID and secret and inputted it into the GliaSandbox connector

-GliaSandbox connector is the Select Connector for the live agent handoff

-Webhook is set to GliaSandbox, UID from webhook is retrieved and is inputted into live agent handoff

 

Perhaps the Queue ID or even the Site ID is incorrect? Not sure what else the issue might be


varockiasamy
  • Employee
  • February 26, 2026

You can find the site ID in the Settings section in your instance and you can find the queue ID under the queue section.

As for the secret make sure that it is within the character limit which is 40 characters. More information on this can be found here.

As for access guide, you can find that document here.


  • Author
  • Participating Frequently
  • February 26, 2026

Hi, i generated a new api key and secret from Glia, I inputted it into the connector, I’m using the webhook token associated with GliaSandbox connector, and I verified that the correct Site ID is being used. Not sure what else there is to try.


  • Author
  • Participating Frequently
  • March 2, 2026

@varockiasamy Hi, wondering if you have any thoughts on how best to solve this? Thank you