You can now filter documents retrieved via the /documents endpoint by using the following query parameters:

• document_type - documents of the specified document_type will be returned.
• from_available_date - documents with available_date on or after this timestamp will be returned.
• to_available_date - documents with available_date on or before this timestamp will be returned.

See our documentation for listing documents to learn more.

Argyle has introduced a new users.fully_synced webhook.

Use the users.fully_synced webhook to be notified when data retrieval has completed for all accounts connected by a user.

See our webhooks documentation for users to learn more.

Argyle has introduced a new breaks array of objects within all_timestamps for the /activities endpoint. Breaks taken during a work shift are represented as objects within breaks. See activities in Argyle Docs to learn more.

Argyle has introduced the new /income-totals endpoint, a major upgrade to how you access annual pay data.

Understanding users’ total annual income can be fundamental, but this information is not always available when viewing individual paystubs. Through the /income-totals endpoint, Argyle looks across all paystubs to provide standardized, aggregated yearly income values. See Income Totals in Argyle Docs to learn more.

Argyle has added retired as a possible value for the employment object's status attribute. See Employments to learn more.

User tokens underpin the returning user experience in Argyle Link, allowing re-authentication without submission of credentials.

On September 29, 2022 Argyle will reduce the expiry time of user tokens.

For returning users, their userId should be used to generate a new user token every time Argyle Link is initialized. This will not impact implementations already following this pattern.

Argyle has added the fields accept_at and cancel_at to the objects all_timestamps and all_datetimes. These fields provide more details on user activity returned by the /activities endpoint. See Activities to learn more.

Argyle has released these API improvements:

• You can now trigger errors in Sandbox mode directly in Console or via the API. Use this feature to understand and tailor error handling in your implementation. See the Sandbox guide to learn more.
• The bank_name field is now available in the bank_account object. See Pay allocations to learn more.

You can now enable instant payout to cards in the Direct deposit switching experience, even if you do not have PCI DSS compliance. Through an integration with Unit, Argyle retrieves the data needed in the background using the card_source object, without the need for you to handle sensitive data. See the documentation on the card_source object for more information.

Argyle has added the destinations array of objects to the /payouts endpoint. destinations details how the user’s net pay is distributed. See the Payouts endpoint documentation to learn more.