As part of Argyle's API improvement initiatives, the /finances endpoint has been removed. This endpoint has already been deprecated as of June 10, 2021.

Argyle recommends reviewing your implementation to ensure that you are not using this endpoint. Reach out to your Customer Success Manager if you would like to discuss alternative endpoints regarding this data.

As part of Argyle's API improvement initiatives, the /finances endpoint will be removed on July 1, 2022. This endpoint has already been deprecated as of June 10, 2021.

Argyle recommends reviewing your implementation to ensure that you are not using this endpoint. Reach out to your Customer Success Manager if you would like to discuss alternative endpoints regarding this data.

Webhooks are now 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.

Argyle would like to remind customers that 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 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.

In December, Argyle issued an API update informing clients of the removal of the count parameter from the Activities endpoint. In that same update, Argyle indicated that they would be removing this parameter from all other APIs in Q1 2022.

As part of Argyle's API improvement initiatives, and to guarantee better retrieval performance, they are now finalizing the removal of the count parameter from all remaining APIs. This change will come into effect on March 31, 2022.

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

Please update your implementations to make use of the new pagination model to avoid any disruption.

Furthermore, in an effort to avoid confusion and reduce complexity, Argyle will be removing two additional undocumented parameters from our API on the same date. These are the is_active parameter from the Webhooks endpoint, and the permissions parameter from the Accounts endpoint. These were undocumented parameters and Argyle is now removing them to bring clarity to the Argyle API. Please review your implementations to ensure you are not making use of these parameters.

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.