Genesys Cloud - Main

Hello Genesys Team,

We're currently exploring the legacy Web Chat v2 API for initiating or transferring chat sessions. Our objective is to route a customer from one organization to another using the following endpoint:

POST /api/v2/webchat/guest/conversations

🎯 Objective

Create a guest chat conversation via API, with plans to eventually transfer it between organizations.

🔧 API Usage

We're using the following payload to initiate the conversation:

{ "organizationId": "", "deploymentId": "", "routingTarget": { "targetType": "QUEUE", "targetAddress": "TEST_Validation" }, "memberInfo": { "displayName": "Joe Dirt" } }

⚠️ Issue

When executing the request, we receive the following error response:

{ "message": "Error accessing web deployment.", "code": "bad request", "status": 400, "contextId": "2ba8782a-7009-4c3f-b86b-114fff0431ac", "details": [], "errors": [] }

We've confirmed that tokens are not a prerequisite for this endpoint, as it supports unauthenticated requests. However, the error seems tied to deployment access or configuration.

Could you please assist in:

• Clarifying if any additional setup is required given the pending deprecation of this API.

Appreciate your support and looking forward to your guidance.

Best regards,
Mahmoud

Hello Genesys Team,

We're currently exploring the legacy Web Chat v2 API for initiating or transferring chat sessions. Our objective is to route a customer from one organization to another using the following endpoint:

POST /api/v2/webchat/guest/conversations

🎯 Objective

Create a guest chat conversation via API, with plans to eventually transfer it between organizations.

🔧 API Usage

We're using the following payload to initiate the conversation:

{ "organizationId": "", "deploymentId": "", "routingTarget": { "targetType": "QUEUE", "targetAddress": "TEST_Validation" }, "memberInfo": { "displayName": "Joe Dirt" } }

⚠️ Issue

When executing the request, we receive the following error response:

{ "message": "Error accessing web deployment.", "code": "bad request", "status": 400, "contextId": "2ba8782a-7009-4c3f-b86b-114fff0431ac", "details": [], "errors": [] }

We've confirmed that tokens are not a prerequisite for this endpoint, as it supports unauthenticated requests. However, the error seems tied to deployment access or configuration.

Could you please assist in:

• Clarifying if any additional setup is required given the pending deprecation of this API.

Appreciate your support and looking forward to your guidance.

Best regards,
Mahmoud

Hello Genesys Team,

We're currently exploring the legacy Web Chat v2 API for initiating or transferring chat sessions. Our objective is to route a customer from one organization to another using the following endpoint:

POST /api/v2/webchat/guest/conversations

🎯 Objective

Create a guest chat conversation via API, with plans to eventually transfer it between organizations.

🔧 API Usage

We're using the following payload to initiate the conversation:

{ "organizationId": "", "deploymentId": "", "routingTarget": { "targetType": "QUEUE", "targetAddress": "TEST_Validation" }, "memberInfo": { "displayName": "Joe Dirt" } }

⚠️ Issue

When executing the request, we receive the following error response:

{ "message": "Error accessing web deployment.", "code": "bad request", "status": 400, "contextId": "2ba8782a-7009-4c3f-b86b-114fff0431ac", "details": [], "errors": [] }

We've confirmed that tokens are not a prerequisite for this endpoint, as it supports unauthenticated requests. However, the error seems tied to deployment access or configuration.

Could you please assist in:

• Clarifying if any additional setup is required given the pending deprecation of this API.

Appreciate your support and looking forward to your guidance.

Best regards,
Mahmoud