cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2317
Views
10
Helpful
2
Replies

Webex Calling Webhooks and Integrations

James McMichael
Level 1
Level 1

I'm playing around with the Webex API in order to show a customer the possibilities of replacing an integration they have using Jabber with Webex.

 

To do this I need Call Events from the telephony_calls resource and a Webhook.

 

The goal is to be able to receive information about external inbound calls, and get the calling party ID to match to a CRM, and to get the times, dates, and durations of calls.

 

I can easily create a webhook for myself and start bringing in this data, however this is not scalable. So I'm looking at using an Integration in order to make the API call for me and create a Webhook for a user.

 

As far as I can see the API just responds with a 400, if I try to define the "owner" as "org", rather than "creator". I have yet to try using creator as the owner, but I suspect that will just end up with the Webhook attempting to return call data for the Integration.

 

The documentation for webhooks for telephony_calls is a bit light, especially on the proper use of filters (I found that using the personId filter didn't give me calls for one user but seemed to only care about calls from that user).

 

Has anyone managed to use the API to create Webhooks on behalf of users, or to successfully use it to create Webhooks as the Integration but limited to a user?

1 Accepted Solution

Rudrakshi
Cisco Employee
Cisco Employee

Hi James,

- As far as I can see the API just responds with a 400, if I try to define the "owner" as "org", rather than "creator".
The telephony_calls resource does not yet support being set as an org level webhook. This is mentioned in on the Create a Webhook reference page in the request parameters section.
ownedBy
string
Specified when creating an org/admin level webhook. Supported for meetings, recordings and meetingParticipants resources for now.

The documentation for webhooks for telephony_calls is a bit light, especially on the proper use of filters (I found that using the personId filter didn't give me calls for one user but seemed to only care about calls from that user).
Not really sure but I believe the personId filter was added to make the future improvements easier.

- Has anyone managed to use the API to create Webhooks on behalf of users, or to successfully use it to create Webhooks as the Integration but limited to a user?
Each user who wants to receive the webhook notifications, would need a webhook created under their individual accounts.
 
Hope you find it helpful.


Best regards,
Rudrakshi Srivastava

View solution in original post

2 Replies 2

Rudrakshi
Cisco Employee
Cisco Employee

Hi James,

- As far as I can see the API just responds with a 400, if I try to define the "owner" as "org", rather than "creator".
The telephony_calls resource does not yet support being set as an org level webhook. This is mentioned in on the Create a Webhook reference page in the request parameters section.
ownedBy
string
Specified when creating an org/admin level webhook. Supported for meetings, recordings and meetingParticipants resources for now.

The documentation for webhooks for telephony_calls is a bit light, especially on the proper use of filters (I found that using the personId filter didn't give me calls for one user but seemed to only care about calls from that user).
Not really sure but I believe the personId filter was added to make the future improvements easier.

- Has anyone managed to use the API to create Webhooks on behalf of users, or to successfully use it to create Webhooks as the Integration but limited to a user?
Each user who wants to receive the webhook notifications, would need a webhook created under their individual accounts.
 
Hope you find it helpful.


Best regards,
Rudrakshi Srivastava

Okay, playing around I cannot use anything that subscribes on behalf of a user.

 

Ideally we need the ability to create webhooks on behalf of users, so that we can as the administrator of our own instance, dynamically create Webex Calling webhooks.

 

So whilst I accept that the answer as it stands is correct, it's not very helpful.