The Request Feed in the Flinks Client Dashboard enables you to see all the users who are connecting their accounts through your integration of Flinks Connect.
In the Request Feed, you can see:
KYC information related to the request
The Request status
Request ID
Your team’s activity
The Financial Institution that the request came from
Date and time that the request was completed

Request KYC and information
The Request Feed provides a high-level overview of who’s connecting in your application. You can see the name, where the request came from, and if you click on the down arrow at the beginning of the row you’ll be able to see some of the KYC information collected in the request.

Request Status
The request status is a real-time indicator of how your users are proceeding through your connection flow. The possible types of status are:
- Completed
- In Progress
- Error
Completed
The Completed state is for requests that have successfully finished collecting information from the user's account and have done so without errors. Example: 
Error
Connections that has issues such as invalid credentials, bank maintenance, and so forth, will have Error Status. To check details for why the connection errors, hover over the error icon. 
In-progress
Connections where the user is in the connection process, such as responding to 2-factor authentication methods, will show as In-progress. Hovering over the loading icon will display what part of the funnel they are in.
Request ID
This is the unique code associated with each request.
Activity
Activity is the Client Dashboard tool for your team's workflow. The Activity column highlights how your team is currently assessing a particular request.

Financial Institution
You can search for institutions by name and filter out financial institutions that you don't want to see. You can also select the connection data type: Banking or Investments.

Date
You can filter your request feed to only show requests from a date period that you specify.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article