This conversation-centric API exposes the resources detailed below. Using the authentication, you will be able to add RESThooks to your Service so that it can respond to Events emitted by a Conversation. These Events will give the possibility for your services to interact with one's Application. According to your accreditation, you will be able to access and modify the applicant's identity documents inside a folder or his Banks Users data.
|Service||Your HTTP server that receives the events|
|Events||Actions fired by the conversation in which your application can respond or not|
|Application||Structure that stores a user's information|
|BanksUser||Structure that gathers all transactions and banking data for a user|
|Folder||Supporting documents for an application|
A Conversation is a list of messages that can be rolled back.
Remotely Accessing and modifying an ever-changing list is a big challenge.
That's the reason why we chose to hide all this complexity behind an Application so you won't have direct access to the resource
Conversation with an API.
As for the resource
ChatFlow, we created an Editor for you to modify it.
This next schema represents the relationship between a Conversation and its Application that are tightly coupled. As the conversation goes on, the application is filled with the required data for the end bank service. Your Service enriches this Conversation by answering to Events triggered by it.