actualbudget/actual

[Bug]: PluggyAI service is using the deprecated `fetchTransactions` method

Open

#8,087 opened on Jun 4, 2026

View on GitHub
 (2 comments) (2 reactions) (0 assignees)JavaScript (7,129 stars) (603 forks)batch import
bank syncbughelp wanted

Description

What happened?

When setting up a Pluggy.ai connection, the account links successfully, but the initial sync immediately fails.

Inspecting the server logs shows the following error:

[Pluggy SDK] HTTP request failed: Response code 410 (Gone) {
  message: 'This endpoint is deprecated. Use GET /v2/transactions with cursor pagination instead.',
  code: 410,
  codeDescription: 'ENDPOINT_DEPRECATED',
  errorId: '[...]'
}
Error fetching transactions: This endpoint is deprecated. Use GET /v2/transactions with cursor pagination instead.

The error appears to originate from the transactions fetch call in the Pluggy integration:

https://github.com/actualbudget/actual/blob/v26.6.0/packages/sync-server/src/app-pluggyai/pluggyai-service.js#L75

The Pluggy Node SDK repository recently added a deprecation notice for the endpoint currently being used:

https://github.com/pluggyai/pluggy-node/pull/165

According to the Pluggy API documentation (https://docs.pluggy.ai/reference/transactions-list-1):

Deprecated: this endpoint is deprecated and will be available only until 2026-12-31, after which it will be removed. Please migrate to GET /v2/transactions, which uses cursor-based pagination.

Although the documented removal date has not yet been reached, the endpoint is already returning HTTP 410 (Gone).

To verify this was not specific to Actual Budget, I attempted to call the endpoint directly through Pluggy's API explorer and received the same response:

This suggests the issue is not with Actual itself, but rather that Pluggy is already rejecting requests to the deprecated endpoint.

Expected behavior

Actual should fetch transactions successfully through Pluggy.ai.

Actual behavior

The account links successfully, but transaction synchronization fails immediately with HTTP 410 because the integration is still using a deprecated transactions endpoint.

Suggested fix

Migrate the Pluggy integration to use the newer GET /v2/transactions endpoint with cursor-based pagination, as recommended by Pluggy.

How can we reproduce the issue?

  1. Setup the Pluggy.ai integration following this: https://actualbudget.org/docs/advanced/bank-sync/pluggyai/
  2. Link an account
  3. See the error

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Desktop App (Electron)

Operating System

Windows 11

Contributor guide