Support

A typo within our return code, which may cause an issue with error mapping.
In the event of a ‘5XX’ error, we’re currently returning: "UK.OBIE.UnExpectedError" (contains upper case 'E' in unexpected). The OB spec shows, that in this scenario, we should be returning "UK.OBIE.UnexpectedError" (no upper case ‘E’ in unexpected).

 This is likely to be fixed as part of the OB spec uplift (uplift to v4). Exact date to be confirmed.

Due to how we translate the date range you may receive a 400 error when requesting 15 months of transaction data. This is likely to occur when requests are made late evening or on weekends.

As a work around please retry your request with +/- 1 day in the date range.

Due to a system limit, if a member has a large number of transactions on their account an error will be returned, rather than returning the members' transactions.

**There is a work around for Third Parties, who will have to request the same data in smaller date ranges to avoid returning an error.

API Affected: GET /accounts/{AccountId}/transactions