Contents
Creating webhooks. To create a new SharePoint webhook, you add a new subscription to the specific SharePoint resource, such as a SharePoint list. The following information is required for creating a new subscription: Resource. The resource endpoint URL you are creating the subscription for. For example, a SharePoint List API URL.
Webhooks are easier to develop and consume than Windows Communication Foundation (WCF) services used by SharePoint Add-in remote event receivers because webhooks are regular HTTP services (web API). Currently webhooks are only enabled for SharePoint list items.
How many webhooks can be fired in SharePoint?
SharePoint webhooks only support asynchronous events. This means that webhooks are only fired after a change happened (similar to -ed events), and thus synchronous ( -ing events) are not possible. If an error occurs while sending the notification to your application, SharePoint retries up to 5 times to deliver the notification.
The notification resource defines the shape of the data provided to your service when a SharePoint webhook notification request is submitted to your registered notification URL. Each notification generated by the service is serialized into a webhookNotification instance:
Handling webhook validation requests. When a new subscription is created, SharePoint validates whether the notification URL supports receiving webhook notifications. This validation is performed during the subscription creation request. The subscription is only created if your service responds in a timely manner back with the validation token.
How to use SharePoint API in Microsoft Graph?
The SharePoint API in Microsoft Graph supports the following core scenarios: Access to SharePoint sites, lists, and drives (document libraries) The SharePoint API exposes three major resource types: