Skip to main content
Back to API List Use this API to fetch translation request and response logs for a bot conversation in ascending order of timestamp within a given date range. These logs help identify and debug issues with translation engine responses.

Path Parameters

Sample Request

Query Parameters

To fetch translation logs, provide at least one of the query parameters sessionId or fromDate and toDate.

Sample Response

Response Parameters

Current Limitations

No pagination metadata in the response

The API doesn’t return fields such as total, count, hasMore, or nextOffset. You must manage pagination manually using offset. If the number of matching records exceeds 50, you must manually fetch the next set by passing offset. Examples:
  • First page: offset=0&limit=50
  • Second page: offset=50&limit=50
  • Third page: offset=100&limit=50

Use UTC timestamps for accurate filtering

For accurate filtering, use fromDate and toDate as full UTC timestamps such as 2026-04-27T18:14:06.498Z.

No translation initiation segregation

The response doesn’t indicate where the translation was initiated from. For example, it doesn’t distinguish whether the translation request originated from:
  • Live Conversation
  • Monitor Interactions
  • Other translation-enabled surfaces
So the API returns translation request and response details, but it doesn’t provide a field for translation initiation source.

Message Order Preservation Limitation

The translated messages are accurate. However, the sequence of messages in the request isn’t preserved due to indexing issues.