Reporting webhooks
What the provider reports back about delivery, and replaying an event.
Note: This screen has no data behind it in this build
The address is specified and the console is ready for it. What is missing is the server side: the reads below are declared by the contract and are not registered in this deployment, so they answer “not implemented” rather than returning anything. Nothing on this page is a placeholder for data — there is no data to place.
What this screen is for
The provider's delivery events — accepted, bounced, complained, opened — with a replay for one this deployment failed to process, which is the counterpart of the billing event inbox for communications.
What has to exist first
- Reads
- staffCommWebhooksList
- Actions
- staffCommWebhookReplay
Each of those is an operation id in the frozen contract. Registering one is a server change, not a permission you can be granted — no group and no scope makes this screen return data today.