Benefits of Webhooks

Every time a user from your organization uploads a document through your internal CRM, you have to manually check the status of the document verification flow in your CRM application. This is just so your agent can complete their underwriting process.

Webhooks allow Ocrolus and your internal systems to communicate with one another. That way any user that uploads a book is automatically notified about the progress of the document being processed.

The Ocrolus webhooks can help bridge the notification process. The Ocrolus webhook API allows you to subscribe to events happening in your account with your integration installed. You can receive notifications of certain events like document or book processing and completion. Webhooks are more scalable than APIs since they are automatic and do not require you to actively keep a track of these events.

How do Webhooks work?

Picture a doorbell system – with a button near the door, and a bell in your living room. When a visitor pushes the button, you hear the doorbell ring, which tells you that someone is at the door – meaning, a signal is sent from the button to the doorbell. Webhooks work on the same concept. The entrance door is an app/site (webhook provider) which sends a signal when a specified event occurs. And the bell in your living room is what is called the “listener”. 

In Ocrolus any event related to the book can be alerted back to the user or the organization via user-defined HTTP callbacks. Whenever an event is triggered related to a book for eg. upon completion of book verification, the webhook sees the event, collects the data, and sends it to the URL specified by you in the form of an HTTP request.

Back to your organization:

Only this time let’s take the example of document processing and verification workflow. Assume that you are processing a book and have the following webhooks to leverage to keep a track of different stages in the document verification workflow:

• VERIFICATION_COMPLETE: Document completes the verification
• BOOK_COMPLETE: All documents in the book have completed verification
• ANALYTICS_COMPLETED: Extraction of analytics is completed

Let’s see how they work in the following scenarios:

1: As a user, you go ahead and upload a document for verification and once the document has completed the verification flow, you receive a notification via email in your inbox letting you know that the verification completed successfully or in case it failed.

2: Let’s say that you want to process multiple bank statements within the same book and track the status upon completion or failure without having to refresh your browser. You can configure a webhook notification to go out on your email and stay updated upon completion of the verification process without having to click a button.

Benefits of using webhooks:

• Get to know that an event has taken place
• Ensure that data is in-sync across multiple web applications that you are using
• Customize the notification system to better suit your user needs
• Connect two or more applications where an event in one application would trigger an event in another application, so on and so forth.

You can configure webhooks by following the article here. You can start by registering your webhook endpoint.