This section outlines the core operational aspects of BlockMark Registry’s webhook system, including costs, retry mechanisms, and attempt ordering.
Webhook costs: Non-test webhooks, meaning any webhook not triggered by the Send Test Webhook feature or not related to a test certificate, incur a small charge per successful attempt (see pricing). Test webhooks are free.
Retry logic: Each webhook attempt (for any webhook type) is retried up to 12 times if it fails, using a capped exponential backoff that increases the gap between retries, with a maximum delay of 1 day. If all 12 attempts fail, the webhook within the webhook group is marked as broken and stops receiving events until fixed. Any webhooks that would have been sent during this period are created with a Pending status. Once the webhook is marked as fixed, the queue resumes, with the last failed attempt (the one that caused the break) added to the start of the queue.
Attempt ordering: All webhook attempts, representing specific actions (e.g., a certificate update) are sent sequentially in the order they are triggered, ensuring consistent and predictable delivery to your endpoint.
Start / pause: Webhooks can be started and paused. Pausing a webhook stops the broadcasting so that you can troubleshoot at your end, but the events are still queued and will be broadcast on restarting. This way, you should not miss any events during the 'paused' period, but will be charged as appropriate on resumption when the webhooks successfully catchup.
Activate / deactivate: Webhooks can be activated and deactivated. Deactivating a webhook stops the broadcasting and does not queue any further events. This way, you will miss any events during the deactivated period.