Conversation Search - Interval Boundary Issue

General Discussion
1

Three coffees. The conversation search endpoint - /api/v2/analytics/conversations/search - is…still not quite right. Specifically, when querying for conversations spanning multiple days, the conversationIds returned are duplicated. Not every conversation, just some. It’s intermittent. Feels like a caching issue, but I’m not seeing anything obvious.

Here’s the call. Simple enough, right?

import requests
import json

base_url = "https://analytics.zoom.us"
api_version = "v2"
bearer_token = "YOUR_TOKEN" # obviously replace

headers = {
 "Authorization": f"Bearer {bearer_token}",
 "Content-Type": "application/json"
}

start_time = "2024-01-01T00:00:00Z"
end_time = "2024-01-03T23:59:59Z"

payload = {
 "intervalBegin": start_time,
 "intervalEnd": end_time,
 "pageSize": 100
}

response = requests.post(f"{base_url}/api/{api_version}/analytics/conversations/search", headers=headers, data=json.dumps(payload))

if response.status_code == 200:
 results = response.json()
 print(json.dumps(results, indent=2))
else:
 print(f"Error: {response.status_code} - {response.text}")

The output shows a bunch of conversations. But some conversationIds show up in both day one and day two results - despite being a single, continuous call. This is throwing off any downstream aggregation. Been down the rabbit hole of the docs. They don’t really cover this edge case. Just says “results may be paginated.” Helpful.

Tried a few things. Here’s a rundown:

  • Zoom Contact Center instance - US region.
  • SDK version - latest.
  • Confirmed the timezone on the server is UTC.
  • Reduced the time range to a single day. Problem disappears.
  • Increased pageSize to the maximum (200). Didn’t change anything.
  • Tested with multiple accounts. Same issue.
  • Double checked the logic of the query. The API calls are being made correctly.
  • Just a hunch - thought maybe the issue was related to the way the data is being indexed internally.

Is it something on our end? Or is this a known bug? It’s been happening for a week now.

1 Like