Notifications
Chainrel offers a versatile notification system that allows you to configure and direct notifications to meet your specific needs. You can customize your notification preferences, ensuring that you stay informed about blockchain events in a way that works best for you. This section will guide you through the process of configuring notifications and provide details about the supported notification channels.
Configuring Notifications
Chainrel gives you the freedom to tailor your notification settings to your requirements. Here's how to configure your notifications:
Backend URL: You can set up notifications to be sent to your backend service by providing the appropriate URL. This option is ideal if you want to integrate blockchain event data directly into your backend processes.
Slack: Chainrel offers seamless integration with Slack, a popular team collaboration platform. You can connect your Slack workspace and receive notifications directly in your Slack channels.
Discord: Chainrel offers seamless integration with Discord, a popular community platform. You can connect your Discord server and receive notifications directly from your Discord channels.
Coming Soon: Telegram, Zapier
How Notifications Works
In Chainrel, notifications are dispatched in the same order as the block events occur. These notifications are directed to the webhook targets you have configured in your account.
Error Handling
Chainrel's notification system includes robust error handling mechanisms to ensure the reliability of your notifications. Here's how we handle errors:
Delivery Failure: If a notification fails to reach the intended recipient (for example, the endpoint URL is unreachable or returns an unexpected status code), it is marked as a failed delivery. In such cases, Chainrel makes repeated attempts to resend the notification until it is successfully delivered.
Notification Status: You can monitor the status of notification deliveries, including successful and failed attempts, from the "Webhook Detail" page available in the dashboard. The "Logs" section provides detailed logs of each delivery attempt, allowing you to track the history of notifications for troubleshooting.
Validating Webhook Deliveries
To ensure the authenticity of webhook deliveries from Chainrel, you can utilize a webhook secret. When a webhook delivery is sent, Chainrel uses your secret token to generate a hash signature, which is included with each payload. You can verify the delivery's authenticity by checking the hash signature provided in the X-Signature-SHA256 header in each delivery. This feature adds an extra layer of security to your webhook notifications. You can find your webhook secret on your webhook's overview page or quickstart page.
Response Time and Status Codes
When your system receives a notification from Chainrel, it should respond promptly with a 200 or 201 status code. This is an acknowledgment that the notification has been successfully received. We expect a response within 5 seconds of the notification request; otherwise, Chainrel will mark it as a failed delivery and make further attempts.
Notification Limits
Chainrel has defined limits to ensure the smooth operation of the platform and fair usage. The specific limits depend on your chosen plan, whether it's the free or paid version. These limits may include the number of events you can monitor, the frequency of notifications. Be sure to review your plan's limits to understand the level of service available to you.
Please be aware that certain blockchain events, such as "Transfer," can occur frequently. This can quickly deplete your account limits. It's important to monitor events carefully to efficiently use your limits and avoid unexpected surprises.
If you choose to deactivate a webhook, please note that during the downtime, you will not receive notifications for events that occurred during that period. Make sure to consider this when deactivating webhooks, as any missed notifications may affect your project's real-time data processing.
Chainrel's notification system is designed to deliver your notifications as reliably as possible, unexpected delays and interruptions may occur. These can be due to various factors, such as system glitches, issues with blockchain RPC nodes, and other service-related hiccups.
Last updated