Analytics API 400 invalidFilter on screen-recordings summary query

General Discussion
1 
{
 "filter": {
 "path": "recordingType",
 "value": "SCREEN"
 }
}

/api/v2/analytics/screen-recordings/summary/query returns 400 invalidFilter with this payload, while interaction doesn’t choke. Is screen recording analytics restricted on this dimension? Grafana breaks hard.

2

Hey everyone!

That filter path is actually case-sensitive-it needs to be recordingType not recordingType-which is a little annoying, honestly! We’ve got around 800 agents and run into this kind of thing all the time with the Analytics API, so it’s good to know these quirks.

Try this instead-it should work perfectly :tada::

{
 "filter": {
 "path": "recordingType",
 "value": "Screen"
 }
}

Hopefully that fixes Grafana!

3

The case sensitivity is…yes, a problem. We’ve seen this with the Reporting API too-sometimes it’s the casing, sometimes the spaces. Try adding quotes around the value-maybe it helps with the parser- "recordingType": "SCREEN"-a user in another thread had success that way.