Webhooks FAQ

Is there a limit on how much data can be sent in a single request?

Yes, there is a limit of 8 MB per request.
However, it is recommended to divide data into smaller-sized payloads and send them in a higher number of requests.
This approach ensures better performance and reduces the likelihood of encountering issues with data transmission or processing.

Are there any constraints on the number of events that can be received via a Webhook?

Rivery handles up to 10,000 events within a 5-minute duration per IP address.
Exceeding this limit may result in dropped events, so it is important to implement appropriate rate-limiting mechanisms on the sender side.

What is the retention time for data posted to the Webhook endpoint?

The data posted to the Webhook endpoint is retained for 72 hours.
After this period, the data will no longer be available for processing.

If the customer posts multiple times to the endpoint before the Source to Target River is scheduled to run, will all data be retained and loaded?

Yes, all data posted to the Webhook endpoint will be retained.
Rivery does not overwrite previously posted data with subsequent posts. When the Source to Target River runs, it will process all retained data up to that point.

What happens if a post request to the Webhook endpoint fails? Is a notification sent to the user?

In the event of a failure, the Webhook endpoint will return an appropriate HTTP response code:

• 500-series codes indicate server-side issues.
• 400-series codes indicate client-side issues.

Rivery does not automatically send notifications to the user. It is the responsibility of the sender's system to monitor these responses and implement a notification mechanism for failed attempts. This ensures that the sender is promptly informed about any delivery issues and can take corrective action.

For additional details or specific use-case questions, please contact our support team.