Webhooks Coming soon
List subscriptions and expiry
Every list webhook subscription on a site: who it calls, when it expires and its client state. Add, renew, edit and remove them, or report across sites to see which integrations depend on which lists. Webhooks do not migrate.
What it does
- Which subscriptions expire in the next 30 days?
- Which external services are listening to this list?
- What has to be set up again after a migration?
How it runs
- Sign in, then choose. Manage one site, or Report across sites.
- Manage. Red under 7 days left, amber under 30. Renew sets up to 180 days.
- Change. Configuration like this has no recycle bin, so ShareMaster re-reads it first, refuses if it changed since you loaded it, saves a backup file before anything changes, asks you, then reads it back. Backups restore from the Backups button. A restored subscription gets a new id.
How it works
Manage reads every list webhook subscription on the site, with its list, notification address, expiry and client state, and colours the days left. Report mode reads the sites you pick and changes nothing; its workbook writes the client state only as present or absent, because it is a shared secret. Backups and JSON exports from the manage page do hold the client state as SharePoint returned it.
Add takes a list, an https notification address, an expiry and an optional client state. A date outside the 1 to 180 days SharePoint allows is moved inside it and you are told. SharePoint itself then calls the address to validate it, and if that fails its own error is shown in full. Editing a subscription to an earlier expiry asks first, and clearing a client state is called out in the question. Renew moves the ticked subscriptions to 180 days from today and skips any that already expire later, so it never shortens one.
Every add, edit, renewal, removal and restore re-reads the subscription, stops if it changed or has already expired and gone, saves a backup file on this computer, asks you, sends the change and reads it back; a failed backup means nothing is sent. More than ten subscriptions in one action asks you to type the count. Each backup records the sign-in account, the credential type and the outcome, and each change goes to the app log.
A removed subscription cannot be recycled. Restoring one from Backups creates it again as a new change, with a new id and an expiry brought back inside the allowed window, and only works if the receiving service answers SharePoint's validation call at that moment.
What you get
An Excel workbook, named like Webhooks 2026-10-07 14-22.xlsx, kept in Report History whether or not you save it.
Summary sheet
Total, expired, expiring and distinct hosts; one row per site.
Webhooks sheet
One row per subscription.
| Column | Example |
|---|---|
| Site | https://contoso.sharepoint.com/sites/hr |
| List | Requests |
| Notification URL | https://hooks.contoso.com/sp |
| Days left | 42 |
| Status | Active |
By endpoint host sheet
Which services depend on which lists.
Refused sheet
Sites or lists that could not be read, with the reason.
What you need
- Manage Lists on the list (Full Control covers it).
- For Add and restore: the receiving service must answer SharePoint's validation request within seconds.
What it will not do
- SharePoint keeps a subscription for at most 180 days.
- Re-creating a removed subscription later needs the receiving service to still be online.
- Webhooks are not copied by a migration.