Article: Customizing Conversation History API Pagination Count- Only On Premise

This article pertains exclusively to the On-Premise Environment and aims to provide information on how to customize the pagination count for the Conversation History API.

Issue Statement
Users frequently need to extract data from the Conversation History API on a daily basis and store it in their data warehouse.

Limitations
The API comes in two versions, one for GET and one for POST methods. The v1 of the API encompasses messages related to all tasks, with a maximum limit of 100 messages per request.

Scenario
The restriction of retrieving only 100 records at a time through our public API poses a significant challenge for users dealing with substantial data volumes. The request here is to enhance the record count or tailor it to specific needs.

Solution
This solution is exclusively applicable to the On-Premise Environment.
If users wish to customize their on-premises environment, they can adjust the value associated with the “DEFAULT_LIMIT” key within the “config/configs/messageStore.json” file.

Please note that it is not feasible to increase this limit in the cloud environment or any of the SaaS instances, such as US, EU, DE, AU, JP.

For detailed information regarding the Conversation History API, please refer to the following document: Reference Document for Conversation History API