Just noticed that POST /api/v2/analytics/interactions/query returns a 400 Bad Request when filtering by custom attributes in our multi-org setup. The error payload indicates an invalid filter syntax for the custom attribute type.
Our integration handles high-volume data exports across several Genesys Cloud organizations using OAuth 2.0. This issue emerged after the recent platform update, affecting our premium app’s reporting module.
We are using the standard JSON filter structure documented in the API reference. However, the response suggests the parser does not recognize the nested attribute path correctly.
Has anyone successfully queried custom attributes with complex data types in the analytics endpoint recently? Looking for a working example or known workaround.