LoginId vs. RequestId (Concept and Data Retention)

Modified on Tue, 6 Oct at 5:28 PM

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 DATE | LOGINID | REQUESTID |

+------------------------+-------------------- --+-----------------+--------------+

| 0001 | 2024-Jan-01 | AAA-AAA-AAA | 111-111-111 |

| 0001 | 2024-Jan-02 | AAA-AAA-AAA | 222-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 without Nightly Refresh is reconnected after 6 months, it will be associated with the same LoginId.
LoginId (Data): The LoginId data is stored indefinitely as long as the client is active