API only returns 404 Not Found

[BrunoTeste]

After updating to V20, we lost the daily schedule of the report by time, where we had the schedule for 9 am, 10 am and so on and then the CSV was imported into BI.
As we no longer have this option, we tried to use the new configurations API to obtain the JSON of the calls, however, it only returns 404 without feedback as to which parameter is invalid.
Has anyone managed to use this API for call reporting?

Request example:

curl -v --location 'https://3CX_FQDN/xapi/v1/ReportCallLogData/Pbx.GetCallLogData(periodFrom=2024-10-18T00:00:00Z,periodTo=2024-10-20T23:59:59Z)?%24top=%3C100%3E&%24skip=%3C0%3E' --header 'Accept: application/json' --header 'Authorization: Bearer api_token'

 

[Evolute IT]

DM me. We have a prebuilt solution for you.

FYI all the parameters are required for the function to work.

 

[Guillaume Bourgeois]

callTimeFilterFrom= and callTimeFilterTo= are strings value, so you need to specify '' if they are empty.

 

[BrunoTeste]

callTimeFilterFrom= and callTimeFilterTo= are strings value, so you need to specify '' if they are empty.

Thanks for the help.
Now I receive a 200, but without information, probably due to the sourceType, destinationType and calltype, testing with 0, 1 and 2 but without success.
I tried looking for Enums in the XML that returns, but there are none. Do you have any other tips on what I can put there?

 

[Guillaume Bourgeois]

I tried looking for Enums in the XML that returns, but there are none. Do you have any other tips on what I can put there?

Have you tried reaching out to ConceptsWeb here ?
Personally, I would start there. If they have documented the various parameters, it will save you a lot of time!
It’s not that I don’t want to help, but I haven’t worked with the 3CX CallLog XAPI yet.
I guided you regarding the string parameters because I quickly noticed some were missing at first glance, after briefly reviewing it (Reverse Engineering).

DM me. We have a prebuilt solution for you.

 

[BrunoTeste]

Have you tried reaching out to ConceptsWeb here ?
Personally, I would start there. If they have documented the various parameters, it will save you a lot of time!
It’s not that I don’t want to help, but I haven’t worked with the 3CX CallLog XAPI yet.
I guided you regarding the string parameters because I quickly noticed some were missing at first glance, after briefly reviewing it (Reverse Engineering).

Thank you very much for your help, I managed to identify what was missing and I can now consume the reports normally!

 

[MartinaP]

Me too, Api return 404 what i wrong?

https://xxxxxxxxx:5001/xapi/v1/Repo...ndDt='2024-11-21T00:00:00Z',waitInterval='0')

 

[edossantos_sipcaller]

Me too, Api return 404 what i wrong?

https://xxxxxxxxx:5001/xapi/v1/ReportTeamQueueGeneralStatistics/Pbx.GetTeamQueueGeneralStatisticsData(queueDnStr='803',startDt='2024-10-18T00:00:00Z',endDt='2024-11-21T00:00:00Z',waitInterval='0')

A 404 error means that the endpoint was not found. 2 options come to my mind:
1) You're using an old version of 3CX not supporting this endpoint yet.
2) You're using a wrong endpoint name.

 

[MartinaP]

Thanks for the reply. I'm using Version 20.0 Update 4 (Build 484 Beta) and I'm referring to the swagger.yaml as the endpoint