In December, Argyle introduced these enhancements in Argyle Console:

Console’s side navigation panel has been refreshed in order to simplify toggling between sandbox and production mode, to allow you to more easily navigate to your account and company details, and to more clearly lay out the different areas of functionality available in Console.

• For faster communication on Link items health, we have introduced two new fields that will be present on the response payload for /link-items endpoint from now on:
• status - will reflect the health of the Link item

• status_details - description of the issue in case the status is not healthy

  We encourage you to set up API polling in order to proactively get the latest updates on Link item issues.

• In order to improve and prepare for product betterment, we are adding two new fields to the payload returned by /pay-allocations endpoint:
• method - the method of the deposit

• card - in preparation for an upcoming feature

  The card object will appear in the payload, but all fields will return null.

• When the user selects a payroll platform already supported by Argyle on Can't find your employer? questionnaire, they will have the chance to directly log in to that specific payroll platform.
• The Login screen now features the show/hide password button to enhance the login experience.
• “Primary” pay allocation is renamed to “Remainder” in order to help the understanding of amount allocations.

As you may be aware, there was a critical bug exploitation with log4j, however, we are happy to inform you that Argyle has not had exposure to this vulnerability and we have taken extra precautions to ensure that all available patches were pushed to production as soon as they were available. In reassurance that we were not affected by the log4j bug:

• Our API is coded in Python, and the API Gateway we use (Traffik) is written in Go. This vulnerability has not impacted them, and we have conducted an internal penetration test to confirm we were not exposed.
• Our broader tech stack contains a small number of Java repositories, and we use Logback instead of log4j. Our Java-based services have not been impacted by this vulnerability.
• As for our broader tooling, only Metabase was listed among the vulnerable apps. This was not exposed to the internet, and we have pushed the latest patched version to production.
• Finally, our hosted Elastic Cloud solution, which does not contain any user data, has been confirmed as not vulnerable. A new patch has been released, and our production cluster is running on this latest version.

API Updates:

• Starting on December 14th, 2021, additional events will be added to the accounts.pay_distribution_failed webhook. This webhook will now be triggered for confirmation_timeout in addition to the pre-existing events. Check out the docs for more information about these new errors on the direct deposit switching failure.
• As part of the migration from the argyle.io domain to the argyle.com domain, the credentials for the sandbox accounts will also change from [email protected] to [email protected].
• New logic to prevent duplicates in the Activity data point will delete duplicates once they are detected. We are adding a new activities.removed webhook that will notify you about the deletion of a certain activity. You will be able to subscribe to the webhook starting from December 16th, 2021. Payload example below:

  {
  "name": "test",
  "event": "activities.removed",
  "data": {
    "account": "017d9bdc-49cb-bcf6-9a99-f3ed32ddb2c2",
    "user": "017d8fed-b702-7675-e9be-00d6b2d24614",
    "available_from": "2019-09-03T17:56:22Z",
    "available_to": "2021-12-09T00:01:01Z",
    "available_count": 1237,
    "removed_from": "2021-09-27T00:22:54Z",
    "removed_to": "2021-09-27T00:22:54Z",
    "removed_count": 1,
    "removed_activities": [
      "017d9f62-84e1-15ad-b269-624458d343c8"
    ]
  }
}

You can find more information in the Webhooks Guide.

• To be even more transparent and give you valuable information, we have exposed the field known_limitations on the /Link-items endpoint that will provide you with any known limitations on the item in question. Learn more about the new object here.
• To make it easier for you to track the allocations set in pay distribution configs, starting December 16th, 2021, we are adding the new field allocation_id to accounts.pay_distributions.updated that will provide you with the respective Allocation ID that was set. You can check out the new payload in the docs.

As part of our API improvement initiatives and to guarantee better retrieval performance, we have disabled the use of the count parameter on the Activities endpoint.

On 16th, December 2021 we will continue the migration and disable count on Payouts, Documents, Employments, Profiles, Vehicles, and Reputations endpoints.

The rest of the endpoints (Link-items, Accounts, Webhooks, and Pay Allocations) will be migrated on the 15th, February 2022.

To paginate bulk fetches from the API, you can use the limit and next parameters to achieve the same result (see Pagination for more information). Please update to make use of the new pagination model to avoid any disruption.

We are migrating argyle.io to argyle.com. The old domain (argyle.io) will continue to operate until February 15th, 2022.

Make sure to replace all requests going to argyle.io with argyle.com.

Make sure to replace Link SDK and Web Link values below as well:

Production: apiHost = "https://api.argyle.com/v1"

Sandbox: apiHost = "https://api-sandbox.argyle.com/v1"

In addition for Web Link SDK:

<script src="https://plugin.argyle.com/argyle.web.v3.js"></script>

• You can now enable your users to search for a different employer even when you are deep linking them to a specific employer. Use Link Customizer in the Console to toggle the display of the Find more employers button for the Login screen.
• The Loading screen that your users see when they connect their accounts has been improved to be more accurate and informative. Now, it displays the time it usually takes to connect an account and communicates the account status during the direct deposit switching authentication process.

• We removed the concept of Primary for percentage allocations from the PD Review and PD Edit screens in Link.

  When your users are prompted with percent allocations, they will see an actual percent value instead of the word "Primary".

• The title and subtitle in the PD Review screen now can be customized through the payDistributionReviewScreenTitle and payDistributionReviewScreenSubtitle parameters, respectively.
• The Can't find your employer? button now can be displayed at the top of the search results list through the showCantFindLinkItemAtTop parameter.

The default value for the allow_add_allocation parameter was changed to false.

Setting allow_add_allocation to true, will add the Add bank account button in the Direct Deposit Switching screen of Argyle Link.

New inactive value was added to the status field in the Pay Allocations resource.