Known issues

Transactions v2

Links for some providers are not working as intended. This will be resolved soon.

Incorrect base URL for page links

For some providers, the Transactions v2 product currently returns link-based pagination with the wrong base URL as part of the href. In the following example, the href is wrong when using the v2 transactions endpoint:

{
    "links": {
        "next": {
            "href": "/fdx/v4/{providerId}/accounts/{accountId}/transactions?offset=eyJ0b3RhbEVsZW1lbnRzIjoxNDk3LCJvZmZzZXQiOiIjUF8yMDIxMDMyM18xOTE1MDI5In0=&startTime=2020-02-14T00:00:00Z&endTime=2022-02-09T00:00:00Z"
        }
    },
    "transactions": [ ... ] 
  }

The links.next.href currently returns a /fdx/v4/{providerId}/accounts/{accountId}/transactions format whereas it should be returning a /transactions/v2/{providerId}/{accountId} format.

A work around would be to extract the providerId and accountId from the current href and to construct the correct next page link using the v2 base URL.