Error creating Org-level Webhook for 'telephony_calls' resource

[krkrks]

Hi everyone,

I am currently trying to set up a webhook to monitor call events using the telephony_calls resource. Since these are telephony events, I assumed I could configure this at the Organization level to capture events for the organization, so I specified "ownedBy": "org".

However, when I ran the following request, I received a 400 Bad Request error.

What I tried:

curl -L --request POST \
--url https://webexapis.com/v1/webhooks \
--header 'Authorization: Bearer [MY_ADMIN_TOKEN]' \
--header 'Content-Type: application/json' \
--header 'Accept: application/json' \
--data '{
"name": "test",
"targetUrl": "https://test.test",
"resource": "telephony_calls",
"event": "created",
"filter": "state=alerting",
"ownedBy": "org"
}'

The Error:

{
  "message": "POST failed: HTTP/1.1 400 Bad Request ... error = 'Org webhooks are not allowed for the given resource type')",
  "errors": [
    {
      "description": "POST failed: HTTP/1.1 400 Bad Request ... error = 'Org webhooks are not allowed for the given resource type')"
    }
  ]
}

My Questions:

1. Based on this error, is it correct to interpret that the telephony_calls resource strictly does not support "ownedBy": "org"?

2. If the above is true, does this mean that if I want to trigger webhooks for all agents (e.g., a team of users receiving calls), I must register a separate webhook for each individual user?

I would appreciate any clarification or best practices regarding this limitation.

Thanks.

[Janos Benyovszki · Accepted solution]

@krkrks you are correct, telephony_calls webhooks are not yet supported on an org level. There is a Feature Request for the same here https://ciscocollabcustomer.ideas.aha.io/ideas/WXCUST-I-8154 , where Product Management confirmed that it's coming next year. Please check.

[krkrks]

Thank you for the confirmation and the link.
I understand that org-level webhooks are not currently supported but are planned for next year.

It is very helpful to know the roadmap.
I will vote for the Feature Request and keep an eye on it.

Thanks again for your help!