Jump to: navigation, search

History REST API

The History REST API is deprecated in 9.0.0 and will be discontinued in a future release.
Starting in, Cassandra support is deprecated in Genesys Co-browse and Redis is the default database for new customers. Support for Cassandra will be discontinued in a later release.

Information about every past Co-browse session is available through the REST API, sitting on top of the Cassandra database. The REST API (REST resources) is hosted by the Co-browse Server.

Each session history record (one per session) is identified by a session ID (UUID), which is unique across the Co-browse cluster within any given period of time. This ID must not be confused with the session token (a random 9-digit sequence) that is used to connect the Co-browse session.

The session history ID is attached to the primary interaction, voice or chat, with the "CoBrowseSessionId" key. For development purposes, it can also be found in the logs with the logging level info: "Session created. Token: {} Id: {}". Full session history is available after a session is deactivated. You can set how long session history is kept in the database and available through the REST API with the retention policy configuration options.

In this initial release of Genesys Co-browse, the REST API is simple but it will be extended in future releases.

Get session history


HTTP method: GET
Resource: /history/sessions/{sessionHistoryId}

  • sessionHistoryId - session history identifer (UUID)

Example request:


HTTP/1.1 200 OK
Date: Thu, 19 Sep 2013 12:21:19 GMT
Content-Type: application/json;charset=UTF-8
Transfer-Encoding: chunked
Server: Jetty(8.1.8.v20121106)

Timestamps are Unix timestamps in milliseconds.

Duration is in seconds. For the first page in a Co-browse session it starts counting when Co-browse session starts and for the last page it ends counting when the Co-browse session ends.

This page was last modified on June 25, 2019, at 11:16.


Comment on this article:

blog comments powered by Disqus