Packet Pacing on Cisco Webex Board

In order to narrow down the data that you receive from webhooks, you can add filters to your webhooks. To do this, you can create a webhook for a resource that applies to an event, and then add a filter or a combination of filters to send you only notification content that is based on the added filter restrictions. For example, you can register a webhook for a membership resource and then add filters so that the webhook only applies to a specific room, by using the roomId or roomType filter.

You can also use more than one filter for a webhook. For instance you can create a webhook and add a combination of filters so the webhook sends notifications only when a specific person (by personId or personEmail) posts a message in a specific room (by roomId or roomType). To add multiple filters for a resource, separate them by using the “&” symbol. For a reference table of available filters you can use, see Resources, Events & Filters below

  • Incoming Webhooks

    If your organization uses the Cisco Directory Connector to synchronize Webex Teams user accounts with Active Directory accounts, then you cannot create or delete Webex Teams users via the People API.

  • Incoming Webhooks

    If your organization uses the Cisco Directory Connector to synchronize Webex Teams user accounts with Active Directory accounts, then you cannot create or delete Webex Teams users via the People API.

  • Incoming Webhooks

    If your organization uses the Cisco Directory Connector to synchronize Webex Teams user accounts with Active Directory accounts, then you cannot create or delete Webex Teams users via the People API.

  • Incoming Webhooks

    If your organization uses the Cisco Directory Connector to synchronize Webex Teams user accounts with Active Directory accounts, then you cannot create or delete Webex Teams users via the People API.

  • If your organization uses the Cisco Directory Connector to synchronize Webex Teams user accounts with Active Directory accounts, then you cannot create or delete Webex Teams users via the People API.

  • If your organization uses the Cisco Directory Connector to synchronize Webex Teams user accounts with Active Directory accounts, then you cannot create or delete Webex Teams users via the People API.

  • If your organization uses the Cisco Directory Connector to synchronize Webex Teams user accounts with Active Directory accounts, then you cannot create or delete Webex Teams users via the People API.

  • If your organization uses the Cisco Directory Connector to synchronize Webex Teams user accounts with Active Directory accounts, then you cannot create or delete Webex Teams users via the People API.

  • If your organization uses the Cisco Directory Connector to synchronize Webex Teams user accounts with Active Directory accounts, then you cannot create or delete Webex Teams users via the People API.

  • If your organization uses the Cisco Directory Connector to synchronize Webex Teams user accounts with Active Directory accounts, then you cannot create or delete Webex Teams users via the People API.

  • If your organization uses the Cisco Directory Connector to synchronize Webex Teams user accounts with Active Directory accounts, then you cannot create or delete Webex Teams users via the People API.

  • If your organization uses the Cisco Directory Connector to synchronize Webex Teams user accounts with Active Directory accounts, then you cannot create or delete Webex Teams users via the People API.

You can only use ID filters for resources you have access to. If you do not have access to a particular resource or ID filter, you will receive an error (such as invalid value for filter: roomId) from the Webhooks API. Alternatively, Cisco Webex Webhooks also supports what is commonly known as a “firehose” or “wildcard” webhook, which allows your app to subscribe to all resources and/or events with a single webhook. For more information, see Using the Firehose Webhook.

Fig. 1: Lorem ipsum dolor sit amet, consectetur adipiscing elit. Vestibulum scelerisque vitae ante in molestie.

Maecenas venenatis quam tempor augue vehicula, nec volutpat velit posuere. Suspendisse potenti. Vestibulum vel libero lectus. Suspendisse ipsum nibh, ultricies porta maximus sit amet, tempor eget sem.

In hac habitasse platea dictumst. Maecenas porta sollicitudin diam, sit amet posuere diam consequat sed. Vestibulum ac leo eu libero tristique convallis. Nulla facilisi. Vestibulum ac leo eu libero tristique convallis. Nulla facilisi.

Yes
No