Is it possible to mix cursor and page-based pagination on /api/v2/analytics/conversations/details/query without the SDK throwing a 422?
Context:
building a presence sync bot for Teams. pulling conversation details to map agent status changes. using python-sdk 3.0.12 against euw2.platform.genesys.cloud. the first two requests work fine. third request fails hard.
analytics_api = platform_client.AnalyticsApi()
body = {
"query": "type:conversation from-date:'2023-10-01T00:00:00Z' to-date:'2023-10-01T23:59:59Z'",
"size": 1000
}
res1 = analytics_api.post_analytics_conversations_details_query(body)
body["cursor"] = res1.next_page
res2 = analytics_api.post_analytics_conversations_details_query(body)
the docs say cursor pagination is default now. but my payload keeps getting rejected with {"code":"invalid_request","message":"cursor and page parameters cannot be used together"} even though i’m not passing a page param. the SDK seems to inject page: 1 automatically when a cursor exists.
Question:
how do i stop the client from auto-appending the page field? i don’t see a config flag to disable it. tried overriding headers and passing page=None but it just gets stripped out. looking for a workaround in the request config.