Returning users to Link
Embedded Link
If you are embedding Link within your website or application, users can be sent directly to an account by including the optionalaccountId parameter in your Link initialization code.
How to retrieve an Account ID.
How to retrieve an Account ID.
- Account ID’s can be retrieved via the API.
- Account ID’s can also be copied from Console: Click the three vertical dots on an account card after selecting an individual user.


Invites
If the user was originally sent an invite via Console or via the API, the user can return to Link any time using the same URL hyperlink included in the invite, which does not expire.If the original invite is lost, it can be resent to the user through Console or via the API. Sending a new invite to the same user will result in duplicate users and should not be used to reconnect disconnected accounts.


Shareable URLs
If a user originally reached Link through a shareable URL, the user can return to Link and access, manage, and reconnect their accounts through the same original URL hyperlink. A copy of the shareable URL associated with an individual user can be found in the Connections page of Console. See the reconnecting users section of our Shareable URLs Guide for more information.Adjusting Link’s initial screen
The following customization is only available for Web implementations of Link.
- Create or edit an existing Flow in Console.
- Toggle OFF the General Setting that says: “Show Your connections as the initial screen for returning users.”
- Save the Flow, copy its Flow ID, and include it in your Link initialization using the
flowIdoptional initialization parameter.

Why accounts disconnect
Argyle’s platform keeps every payroll connection alive for as long as the associated payroll system allows. Once a user connects a payroll account, the connection stays alive indefinitely whenever possible. This allows Argyle to continuously scan and retrieve any new data that is added to the user’s payroll account, giving you ongoing data refreshes as new paystubs or payroll documents become available.Similarly to how bank account connections with third party apps need to be refreshed periodically, some payroll systems require users to re-authenticate their connections from time to time. If an account becomes disconnected, payroll data can still be retrieved via Console or the API, but ongoing data refreshing will be paused until the account is reconnected by the user.
Types of disconnections
Re-authorization needed
Some payroll systems have automatic log-outs after a set period of time. Once Argyle scans a connected payroll system and finds the user has been logged out, both Console and the API will display anauth_required error in the account’s details:

- If a disconnection occurs, have the user return to Link.
- The user can re-establish the connection by simply selecting Reconnect. No need to re-submit login credentials!

90% of all payroll accounts require that users complete an additional multi-factor authentication (MFA) step.
Expired credentials
Some payroll systems require users to reset their passwords periodically. When this occurs, anexpired_credentials error will be shown in the account’s details.
- When credentials expire, have the user return to Link.
- On the account’s login screen, a Login help button will take the user to their payroll system’s platform. After the user resets their username or password, they need to return to Link and enter their updated credentials to re-establish the connection.

Simulating disconnections
When Console is in Sandbox mode, Flows provides an error testing feature that lets you simulate account disconnections. Visit our Sandbox Testing Guide for more information on error testing in Console and via the API.Revoking access
Users can revoke access to their accounts at any time by emailing us at [email protected].
If an account is revoked by the user, or deleted via Console or via the API, and the user later connects the same payroll account in Link, a new account ID will be created that is distinct from the original revoked/deleted account.

Webhooks
We recommend subscribing to theaccounts.updated webhook to be notified when an account becomes disconnected.
When subscribing, make sure to set
include_resource to true using the config parameter to always receive a payload with the updated account’s details.accounts.updated webhook was triggered by an account disconnection:
- Examine the
connection.statusfield of the account object included in the webhook payload. - If the value of
connection.statusiserror, and theerror_messageis eitherauth_requiredorexpired_credentials, an account disconnection has occurred.
accounts.removed webhook to be notified when a user revokes access to one of their connected accounts.