LoginId vs. RequestId (Concept and Data Retention)

Modified on Wed, 13 Mar at 9:43 AM

Concept:
  • LoginId: The LoginId is a token that represents the end-user card. A new token is generated based on 4 variables: instance, institution, language and user name.
  • RequestId: The RequestId is a token that represents a connecting session. This session can retrieve live data (Flinks Connects or Nightly Refresh session) or cached data (API calls).
CARD (LAST 4 DIGITS)CONNECTION DATELOGINIDREQUESTID
00012024-Jan-01AAA-AAA-AAA111-111-111
00012024-Jan-02AAA-AAA-AAA222-222-222



Data Retention:
  • LoginId (Token): The LoginId token doesn't expire. It will only stop existing if the DeleteCard API is called. This means that when a card which doesn't have the Nightly Refresh enabled is reconnected after 6 months,  this card will be associated with the same LoginId.
  • LoginId (Data): The LoginId data is stored for 90 days, which is counted from the last successful live call (Flinks Connect or Nightly Refresh session).


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article