API Bugs

[emansih]

Hello. I was playing around with the API and I have possibly found some bugs?

When calling the /v1/accounts end point, I applied a HOME_LOAN filter and the API returns me both TRANSACTIONAL and SAVER accout type. Is it working as intended?

Steps to produce:

curl --location --globoff 'https://api.up.com.au/api/v1/accounts?filter[accountType]=HOME_LOAN' \
--header 'Authorization: Bearer XXXXXXXXX'

When calling the /v1/transactions endpoint, I supplied a date that does not exist - 31 Feb 2024, the API returns me data in 1 March 2024. The API fails to return data if I supply 32 Feb 2024, which is working as intended.

Steps to reproduce:

curl --location --globoff 'https://api.up.com.au/api/v1/transactions?filter[since]=2024-02-01T15%3A00%3A00.05%2B11%3A00&filter[until]=2024-02-31T15%3A00%3A00.05%2B11%3A00' \
--header 'Authorization: Bearer XXXX'

Returns a response with HTTP 200 OK. Note the filter[until] date is 2024-02-31, which is impossible

curl --location --globoff 'https://api.up.com.au/api/v1/transactions?filter[since]=2024-02-01T15%3A00%3A00.05%2B11%3A00&filter[until]=2024-02-32T15%3A00%3A00.05%2B11%3A00' \
--header 'Authorization: Bearer XXXXX'

Returns a response with HTTP 400 Bad Request. This is working as intended as the filter[until] date is 2024-02-32 which does not exist.

[markbrown4]

Thanks for raising, will get fixes for these deployed today.