LogoLogo
  • 👋START HERE
    • Welcome!
  • ℹ️General
    • Release Notes
      • Full Feature Base Template
      • Services
      • Rule-based Automation
        • May 2025
        • February 2025
        • January 2025
        • December 2024
        • November 2024
        • October 2024
        • September 2024
        • August 2024
        • July 2024
        • June 2024
        • May 2024
        • April 2024
        • March 2024
        • February 2024
        • January 2024
        • 2023
        • 2022
        • 2021
        • Dialog Design Update
    • Glossary of Terms
    • Authentication Methods
      • SSO (Single Sign-On)
      • Built-In User Management
    • Acceptable Use Policy
  • ⚙️Rule-based Automation
    • Overview
      • Account Settings
        • Profile
        • Team
        • Roles and Permissions
          • User Management
          • Project Permissions
      • Basic Concepts
        • Project Management
        • Version Management
        • Multi-Lingual Bots
          • Supported Languages
        • Managing User Interactions
          • Unexpected User Input
          • No User Input
    • Dialog Interface
      • Blocks
        • Conversation Logic
          • Start Conversation
          • Global
          • State
          • Intermediate Response
          • To Previous State
          • End Conversation
        • Subdialog
          • Reusable Subdialogs
        • Phone
          • Continue Listening
          • Call Control
        • Technical Logic
          • Service
          • Condition
          • Storage
        • Other
          • Note
      • Speech Assets
        • Intents
          • Utterances
          • Descriptions
        • Slots
          • Custom Slots
            • List Slots
            • Machine Learning Slots
            • Regex Slots
            • LLM Slots
          • Prebuilt Slots
            • DTMF Slot
        • Text Snippets
        • Dictionary
      • Variables
        • Intents
        • Slots
        • Storage
        • Text Snippets
        • Environments
        • Platform
        • Context
      • Services
        • Service Integration Guide
        • Service Development
        • Service Branches and Error Handling
        • Public Services
          • Date and Birthdate Recognition
          • Spelling Post-Processing for Phone
          • IBAN Validation
          • License Plate Validation
          • Address Search
          • Street Names per Postal Code
          • Email Service
          • SMS Service
          • API Adapter
          • Salesforce-Flow Connector
          • Opening Hours
          • Speech-to-Text Hints
          • Fuzzy Match Names
          • Delay Service
      • Debugger
        • Phone 2
        • WhatsApp
        • Textchat 2
    • Environments Interface
      • Service Keys
    • Deployments Interface
      • Creating a Release
      • Editing a Release
    • Text-to-Speech
      • Azure
      • ElevenLabs
      • OpenAI via Azure (Preview)
      • SSML
        • Audio
        • Break
        • Emphasis
        • Prosody
        • Say-as
        • Substitute
        • Paragraph and Sentence
        • Voice
    • Autocomplete
    • Parloa APIs
      • CallData Service and API
      • Conversation History API
      • Textchat V2 API
    • Phone Integrations
      • Genesys Cloud
        • Setting up the SIP Trunk
        • Sending/Receiving UUI Data
        • Creating a Script to Display UUI
      • SIP
      • Tenios
        • Setting Up an Inbound Connection
        • Setting Up an Outbound Connection
        • Transferring a Call
      • Twilio
      • Public IPs and Port Information
    • AI Integration Overview
      • Dual Intent Recognizer (DIR)
      • Dual Tone Multifrequency (DTMF) Intent
    • Analytics and Debugging
      • Understanding Conversations and Transactions
      • Managing Caller ID Data
      • Hangup Events and Triggered Analytics
      • Analytics Transactions: Data Structure and Insights
      • Dialog Analytics
      • Audit Logs
      • Parloa-hosted Analytics
    • Data Privacy
      • Anonymizing Personally Identifiable Information
    • NLU Training
      • NLU Training Best Practices
    • How To
      • Create a Scalable and Maintainable Bot Architecture
      • Implement OnError Loop Handling
      • Resolve the 'Service Unavailable' Error
    • Reference
      • Parloa Keyboard Shortcuts
      • Frequently Asked Questions (FAQ)
      • JavaScript Cheat Sheet
        • Using Regular Expressions (Regex)
  • 🧠Knowledge Skill
    • Introduction
    • Knowledge Collections
    • Knowledge Sources
    • Knowledge Skill Setup
      • Step 1 – Create a Knowledge Skill Agent
      • Step 2 – Configure a Knowledge Skill Agent
      • Step 3 – Configure a Knowledge Skill Agent
Powered by GitBook
On this page
  • Identifying Conversations
  • Accessing the Conversation History
  • Making a Request
  • Response Structure

Was this helpful?

Export as PDF
  1. Rule-based Automation
  2. Parloa APIs

Conversation History API

Fetch the Entire History of a Conversation in a Single Request

PreviousCallData Service and APINextTextchat V2 API

Last updated 11 months ago

Was this helpful?

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 , 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.

Identifying Conversations

Each conversation on the Parloa platform is assigned a unique identifier, known as . 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 , ensuring a unique conversationId is created for each distinct interaction with the same caller.

Accessing the Conversation History

To access the Conversation History via a REST request, you will need the following information:

  • Endpoint: Visit the 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.

Making a Request

Retrieve the conversation history by executing the following curl command in your terminal:

curl --location 'https://app.parloa.com/api/v1/conversation-history/<CONVERSATIONID>' \
--header 'Authorization: Bearer <TENANT-SPECIFIC-TOKEN>'

Response Structure

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:

{
  "conversationId": "<conversation-id>",
  "releaseId": "<release-id>",
  "requesterId": "<requester-id>",
  "userContextId": "<user-context-id>",
  "conversationStart": "<timestamp>",
  "conversationFlow": [
    {
      // Transaction details
    },
    // Additional transactions
  ]
}

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:

{
      "conversationId": "b6b45d30-9b33-422d-b2af-c9d335423cfe",
      "releaseId": "5ea1ab5f3ae50a67bd80c77f",
      "requesterId": "ec0c0d8c-6d2c-4a34-b4c0-2b98bcd7d1f4",
      "userContextId": "5ea1ab5f3ae50a67bd80c780",
      "conversationStart": "2020-04-23T14:51:11.378Z",
      "conversationEnd": "2020-04-23T14:51:11.378Z",
      "conversationFlow": [
        {
          "timestamp": "2020-04-23T14:51:11.378Z",
          "human": {
            "intent": "LaunchRequest",
            "message": "LaunchRequest",
            "entities": {}
          },
          "bot": {
            "message": "Welcome, do you want to book a room?"
          }
        },
        {
          "timestamp": "2020-04-23T14:51:11.378Z",
          "human": {
            "intent": "Affirmative",
            "message": "Yes",
            "entities": {}
          },
          "bot": {
            "message": "Great. For how long?"
          }
        },
        {
          "timestamp": "2020-04-23T14:51:11.378Z",
          "human": {
            "intent": "TellDuration",
            "message": "For fifteen minutes",
            "entities": {
              "duration": "15"
            }
          },
          "bot": {
            "message": "Ok. I have booked room 3b for fifteen minutes"
          }
        }
      ]
    }
⚙️
API specification
callId
conversationId
sessionId