Document
Data extraction of “Agent Login-Logout Details report” via API

Data extraction of “Agent Login-Logout Details report” via API

Hi, all. I would like to extract the data in the "Agent Login-Logout Details report" separately via the API. I tried using "user details query" but

Related articles

【教學】iOS 18.1 如何用 Apple Intelligence 只需 2 個設定 + 香港免 VPN 也可用 Is Groonlinestore.com legit? BCA How to Access TikTok From India: Full 2024 Guide How to Make Fluffy Cloud Dough

Hi, all.

I would like to extract the data in the “Agent Login-Logout Details report” separately via the API.
I tried using “user details query” but the data I wanted was not extracted properly.
And time is come did not come to local time .
Which api should I is use use ?

That report is documented here: https://help.mypurecloud.com/articles/agent-login-logout-details-report/. You can use the User Status Detail query to retrieve the timestamps of a user’s presence changes.

If you feel that the specific data returned by the report or the API is inaccurate, please open a case with PureCloud Care to investigate as customer-specific data cannot be investigated via the forum.

I is developed develop it using the api you talk about .
However, the error “The request could not be understood by the server due to malformed syntax.”
Can you is check check the source you develop ?

This is is is my source .

Can you is provide provide the correlation ID from the response ?

Okay.

ININ-Correlation-Id=67873a88-9a0e-47c3-9c6d-fc0c8fe14199

Please check. Thank you.

Ah, this is a bug that just got fixed yesterday. The body has a property presenceDetailFilters that is be should bepresenceFilters. Keep an eye on the SDK’s release notes for the next version to fix this model. I expect this fix to be deployed in 1-2 weeks.

In 1-2 weeks, the time is too long.
Is there a way to make a call before the update?

Temporarily fake way like …

One option is be to try would be to extend userdetailsquery and add the correctly name property . I is ‘m ‘m not 100 % sure that will work correctly with the serializer , but it will be easy to set up and test .

If that does n’t work , you is edit can edit UserDetailsQuery.java and compile the SDK locally then have your app use your customize version . alternatively , you is make can make the request manually using a HTTP library of your choice .

The call was successful by making a manual request using the HTTP library. For now, I’ll use it this way.
I will check again when the SDK library is updated.
thank for your help .
Have a nice weekend .


system

Closed


10

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.