Radha

Hey,

I am using the endpoint api/v2/ticket_metrics.json to fetch ticket metrics. My goal is to retrieve metrics until the tickets are 7 days old, utilizing pagination. Initially, I used offset pagination, but due to its limitations, I switched to cursor pagination.

However, I am encountering issues with cursor pagination, as each API call takes between 17 to 30 seconds. Upon debugging, I discovered that the API response time is significantly higher with cursor pagination.

Could you please help me understand why this is happening? Is the increased response time due to the use of cursor pagination? How can I resolve this issue? It is crucial for me to reduce the API response time.

Hey,

I am using the endpoint api/v2/ticket_metrics.json to fetch ticket metrics. My goal is to retrieve metrics until the tickets are 7 days old, utilizing pagination. Initially, I used offset pagination, but due to its limitations, I switched to cursor pagination.

However, I am encountering issues with cursor pagination, as each API call takes between 17 to 30 seconds. Upon debugging, I discovered that the API response time is significantly higher with cursor pagination.

Could you please help me understand why this is happening? Is the increased response time due to the use of cursor pagination? How can I resolve this issue? It is crucial for me to reduce the API response time.