The Resend of Rejected Information project aims to enhance the delivery of information to our customers by introducing a system that captures events and summaries not received by the customers. These are stored in designated buckets, enabling customers to proactively request and retrieve any pending documents. Our goal is to minimize information loss and ensure effective data delivery.
Key features and operation
The operation of the project involves several key steps:
Initial document sending: Events and summaries are initially sent to the customer via webhook. If these documents are not received properly, a retry process is initiated.
Retry process: This includes up to three attempts to deliver the document within specific intervals (after two, 24, and 48 hours). If unsuccessful, the document is moved to a storage bucket based on the operational environment (sandbox or production).
Storage in buckets: Unreceived events and summaries are stored in respective environment buckets, available for customer retrieval for three days in the sandbox and ten days in production.
Customer notifications: Notifications are sent via webhook to alert customers of pending events and summaries awaiting acceptance in the buckets.
Preference management: Customers can manage their notification preferences. Even if notifications are turned off, unreceived events and summaries are still stored under the same time rules.
Endpoint registration
Clients can register their notification webhook by contacting their account manager through an official channel.
Endpoint features
For the endpoint to successfully receive information from ROOK, it must adhere to the following criteria:
Method: POST
Authentication: No authentication required.
Response: The endpoint must respond with HTTP status codes 200, 201, or 202 to be considered a valid response.
Body: There are no restrictions on the format or content of the message body.
Frequently asked questions
What is the goal of the Resend Reject Information project?
The project seeks to improve information delivery by ensuring customers receive comprehensive data about their users, maintaining communication even when initial attempts fail.
How is information loss prevented?
By storing unaccepted documents in buckets, customers can proactively request and retrieve any pending documents, thereby mitigating the risk of information loss.
How long are documents not received by the client kept?
Documents are stored in their respective buckets within their environment for ten days in the production bucket and three days in the sandbox bucket.
What is the process for handling resend attempts before storing documents in the bucket?
Before moving documents to the bucket, a retry process is implemented, involving two attempts to deliver the document at intervals of two and 24 hours.
How does the project ensure effective communication with customers regarding pending documents?
The system uses webhooks to notify customers of pending events and summaries, and customers can also request the resend of documents through a designated endpoint.
How does the project differentiate between sandbox and production environments?
Separate buckets and endpoints are established for each environment to ensure appropriate handling of documents.
How can I subscribe to these webhook notifications?
Currently, subscriptions to webhook notifications require a manual setup. Please provide us with a URL where you would like notifications to be sent.