cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
780
Views
11
Helpful
3
Replies

Webex Contact Center for Developers API

donnytheguy
Level 1
Level 1

Hello, I'm trying to use the Search API in Postman to test some of the queries I can use in GraphQL to use in a project. I'm getting a 200 response in Postman now, but no matter what I change my GraphQL code too, I can't generate any data. I was wondering if there was some Webex Dashboard that could show me what data I'm querying? I've copied and pasted numerous samples from the Gitub/webex-contact-center-api-samples page but I can't get any data in my response. Also wondering if there's some setting I need to enable to start logging data that the Search API uses? 

1 Accepted Solution

Accepted Solutions

Link to the Reporting lab - 

https://wxcctechsummit.github.io/wxcclabguides/TechSummitRoW_2021/Analyzer.html

 

The search API is nothing but a historical / realtime REST API that displays data, powered by the same backend as Analyzer.

View solution in original post

3 Replies 3

Arunabh Bhattacharjee
Cisco Employee
Cisco Employee

Hi @donnytheguy  what is the error / issue you are seeing? 

Any snippet of the search query? you'll need actual call data and mandatory to: and from: parameters to pull the data.

If it is working on postman and not working on the developer portal, please confirm the orgId and the developer portal URL in use. It may be something basic.

 

Yes oyou can use Analyzer to check the reporting data, there is a detailed analyzer lab here, I would recommend going through all 5 sections.

 

Thanks & Regards,

Arunabh.

Screen Shot 2022-08-03 at 5.26.11 PM.png

Link to the Reporting lab - 

https://wxcctechsummit.github.io/wxcclabguides/TechSummitRoW_2021/Analyzer.html

 

The search API is nothing but a historical / realtime REST API that displays data, powered by the same backend as Analyzer.

donnytheguy
Level 1
Level 1

Thanks Arunabh,

Link was helpful, found out the issue was I was using the wrong endpoint URL - it was pointing to the wrong server that our calls are not logged in. Changed the Region in the URL and it works fine now!

Thanks for the replies,

Donny Miller