Chats & Transcripts

When making calls to the Ebbot API, the full API key needs to be passed as a header namedx-api-key:

x-api-key: <public-key>.<secret-key>

Fetching chats and transcripts

Two API endpoints are available:

  • List Chats: Retrieves a paginated list of chats.

  • Fetch Transcript: Retrieves the full transcript for a specific chat ID.

Step 1: Retrieve a List of Chats

The URL in the following endpoints needs to be replaced with your actual Ebbot Platform URL. This is the same URL used to reach ebbot app. It can be one of the following URLs:

ebbot.eu v2.ebbot.app ca.ebbot.app

Endpoint

GET https://<ebbot_url>/api/chats/company_chats?page={page_number}&limit={limit}
  • page (optional): Page number for pagination (default is 1).

  • limit (optional): Number of chat records to retrieve per request (default is 15).

Example Request (curl)

curl --location 'https://ebbot.eu/api/chats/company_chats?page=1&limit=15' \
--header 'accept: application/json' \
--header 'x-api-key: <public-key>.<secret-key>'

Step 2: Retrieve Chat Transcript

Use chat IDs from the chat list response to retrieve detailed transcripts.

Endpoint

Replace {chatid} with the desired chat ID.

Example Request (curl)

Example Transcript Response

Rate Limit

To ensure optimal performance and availability of the Chats API, a rate limit is enforced:

Limit: 20 requests per minute

Exceeding this limit will cause subsequent requests to time out. Please manage your request rates accordingly to avoid disruptions in service and implement handling mechanisms to pause and retry after the rate limit resets.

Last updated

Was this helpful?