Open a test session against a deployed Copilot
Mints one test contact against the Copilot’s deployed endpoint - a fresh userId/sessionId pair, the endpoint’s urlToken, and the socket and Agent Copilot workspace addresses the Review tab drives it with. Every call is a different contact (“open”, not “read”), and the operation answers 409 while the config has been saved but its deploy has not landed yet.
Authorizations
Supply the API Key in the HTTP-Header
Headers
The Accept header specifies the media type that the client expects in the response. Available options: application/json, application/hal+json, application/xml, text/xml, text/csv. The default value is application/json.
application/json, application/hal+json, application/xml, text/xml, text/csv Path Parameters
The unique identifier for the Copilot config.
24^[a-z0-9]{24}$Query Parameters
The unique identifier for the Project. Copilot configs are always scoped to a single Project.
24^[a-z0-9]{24}$Response
Returns a test session.
One test contact against a deployed Copilot. Every call mints a NEW userId/sessionId pair - this is "open", not "read" - and hands out the endpoint's urlToken, which no other Copilot config response carries. There is no transport of Cognigy's own here: both the socket (opened with this response's socket block) and the Agent Copilot workspace iframe (opened at workspaceUrl) talk to the endpoint host directly with the same ids.
The deployed endpoint's own address, for display and as a REST fallback.
The endpoint's address token.
The Agent Copilot workspace, already carrying this session's ids - the iframe's src exactly as given.
Where the Review screen opens its socket, and what with.
What the last deploy built. Empty for a Copilot deployed before this was recorded.
Unix timestamp in seconds, matching the config's publication.