Conversation History API
Fetch the Entire History of a Conversation in a Single Request
Last updated
Fetch the Entire History of a Conversation in a Single Request
Last updated
The Conversation History API offers a streamlined method for retrieving the full history of a conversation through a single GET request. Unlike analytics, which provides data on a per-transaction basis, allowing you to collate records using a unique callId
, the Conversation History API returns all transactions from a conversation in one comprehensive record. Moreover, while analytics captures storage variables and state information, Conversation History focuses solely on conversation-related details such as utterances, prompts, intents, and slot values.
Each conversation on the Parloa platform is assigned a unique identifier, known as conversationId
. This ID is generated upon the detection of a WELCOME event, signaling the start of a new conversation. All subsequent interactions within this conversation are grouped under the same conversationId
until the conversation ends. Additionally, the conversationId
is linked to a specific caller's sessionId
, ensuring a unique conversationId
is created for each distinct interaction with the same caller.
To access the Conversation History via a REST request, you will need the following information:
Endpoint: Visit the API specification for detailed information.
ConversationId: This can be found in the debugger context. For example:
Customer-Specific Access Token: Please contact your Partner Manager or Customer Success Manager to access this service.
Tokens are valid for 1 year from creation by default.
To avoid any service interruptions, monitor the token expiration date and contact support for renewal when necessary.
Retrieve the conversation history by executing the following curl command in your terminal:
The API returns the conversation history in a structured format, detailing each transaction within the conversation, including the exchanges between human and bot, recognized intents, and any storage variables gathered during the conversation. The response is structured as follows:
The following describes each field:
conversationId
: The unique identifier for the conversation.
releaseId
: The identifier for the Parloa release/deployment during which the conversation occurred.
requesterId
: The identifier for the requester.
userContextId
: Identifies the user's lifetime context, allowing linkage of multiple calls from the same user for a cohesive interaction history.
conversationStart
: The timestamp marking the start of the conversation.
conversationFlow
: An array containing the details of each transaction within the conversation.
The following is an example response: