Analytics Jobs API: Missing Participant Attributes in Exported Conversation Details

Architect & Flows
1

I’m running a large batch export using the POST /api/v2/analytics/conversations/details/jobs endpoint to pull historical data for our compliance audit. The job finishes successfully and I’m fetching the results via the signed URL, but I’ve noticed a major gap: the attributes object within the participants segments is empty for almost all conversations.

We use ‘Set Participant Data’ extensively in our Architect flows to store CRM IDs and transaction codes. When I query the same conversation via the standard /details/query endpoint (the non-job version), the attributes are there. Why are they missing from the Job results? Is there a specific property I need to enable in the job request to include participant attributes?

2

We had this exact issue during our PureConnect migration. It turns out that ‘Participant Attributes’ are not included in the Analytics Jobs results by default because they can significantly increase the payload size. You have to explicitly request them by adding "showAttributes": true to your job body.

If you don’t see that field in the SDK documentation, check the API Explorer—it was added as a parameter fairly recently to the Jobs endpoint.

2 Likes
3

Eli is correct. As someone who has been building GC integrations at ConvergeOne for years, I’ve learned that the Jobs API is optimized for speed and volume, so it strips ‘optional’ metadata unless requested.

One warning: enabling showAttributes will double or triple the size of your JSON result file. Make sure your parser can handle large multi-gigabyte files, as the Jobs API will dump everything into a few massive chunks. If you only need attributes for some calls, you might be better off sticking with the Query API and paginating.

1 Like
4

That flag did it. The attributes are now populating correctly in the JSON. Thanks for catching that.

5

Cause: The showAttributes flag increases payload size significantly, which can cause timeouts or memory issues on the SBC side during large exports.

Solution: Check the JSON chunk size. If it exceeds 50MB, consider splitting the query by date range. The API docs mention this limit in section 4.2. Keep an eye on the response headers for Content-Length.

2 Likes