The validity of the URL returned by these fields is reduced to 15 minutes:

• file_url for the /documents endpoint
• file_url for the /reports endpoint
• <file>.url for the /forms endpoint

As of April 20th, webhooks will be sourced from two different IP addresses. If you are subscribed to webhooks and use allowlists, add these IP addresses to your allowlists to avoid any issues:

• 35.188.163.115 - The existing IP address for webhooks, which you may already have on your allowlists.
• 34.122.50.253 - A new IP address for sourcing webhooks.

• As part of Argyle's API improvement initiatives to guarantee better retrieval performance, the count parameter is now removed from all Argyle APIs.

  To paginate bulk fetches from the API, you can combine the limit query parameter and the previous and next page URLs to achieve the same result. Refer to the pagination documentation for more details.

• The is_active parameter is now removed from the /webhooks endpoint to reduce complexity. This parameter was unused and did not have any functionality implemented.

Following up on previously announced changes that will come into effect on March 31, 2022:

• As part of Argyle's API improvement initiatives to guarantee better retrieval performance, the count parameter will be removed from all Argyle APIs.

  To paginate bulk fetches from the API, you can combine the limit query parameter and the previous and next page URLs to achieve the same result. Refer to the pagination documentation for more details.

  Argyle recommends updating your implementations to use the new pagination model to avoid any disruption.

• The is_active parameter will be removed from the /webhooks endpoint to reduce complexity. This parameter is unused and does not have any functionality implemented.

  Argyle recommends reviewing your implementations to ensure you are not using this parameter.

On April 7th, Argyle Link is getting an upgrade. The Argyle team has been hard at work improving the visual experience for Link users. This update is exclusively to enhance Link’s look and feel and will not impact any endpoints or data connection to Console.

Click here to learn about new features coming in Link 4.

Last week Argyle launched the Shiftsmart integration. It can be accessed via shiftsmart Link Item.

To further increase the fidelity of available data, these fields are now available in the /payouts endpoint:

• gross_pay_ytd
• net_pay_ytd

Additionally, the was_connected field is now exposed in the /accounts endpoint.

In February, Argyle introduced these enhancements in Argyle Console:

• The way users’ Pay Allocations are displayed in Console has been updated to help you find relevant information more quickly.
• Settings that were previously spread out across multiple pages have been consolidated into a single Settings area, accessible at any time from the bottom of Console’s side menu.
• You can now switch to Production with ease through the redesigned pricing page in Settings → Billing.
• New Argyle customers will now find three pre-loaded sample users in sandbox mode, featuring example data sets from salaried, hourly, and gig workers.
• You can now add a DDS configuration to Link Emulator to test how direct deposit switching will work in your Argyle Link implementation.

Last week Argyle launched the Patreon and Point Pickup integrations. These can be accessed via the patreon and point_pickup Link Items.

On March 17, 2022, Argyle will expose two new fields in the /payouts endpoint to further increase the fidelity of available data:

• gross_pay_ytd - Gross pay amount received in this calendar year.
• net_pay_ytd - Net pay amount received in this calendar year.

Argyle will also expose a new field in the /accounts endpoint on the same day:

• was_connected - Indicates that the account has been connected.