Transactions timestamp is wrong

[gsalvatori]

Hi all,

just to report that I'm noticing that the transactions timestamps retrieved via api, don't match the actual timestamps on the app. For example, if you take the first transaction from this list (via CLI)

on macbook ~ took 12s
➜ n26 transactions
Output is limited to 5 entries.
Date               Amount      From    To          Message         Recurring
-----------------  ----------  ------  ----------  --------------  -----------
**01/25/22 07:29:28  -8.81 EUR   You     NATURASI'   ATM Withdrawal**
01/24/22 14:28:44  -29.9 EUR   You     PAGOPA      ATM Withdrawal
01/24/22 14:28:44  -9.99 EUR   You     SPOTIFY     ATM Withdrawal
01/24/22 14:28:44  -73.1 EUR   You     PASCAL SRL  ATM Withdrawal
01/24/22 14:28:44  -11.95 EUR  You     EXCELSA     ATM Withdrawal

reports that the transaction was carried out on January 25 but in the app I get Saturday, January 22 (which is the correct date) :

Same example via API:

- id: ..
  userId: ..
  type: PT
  amount: -8.81
  currencyCode: EUR
  originalAmount: -8.81
  originalCurrency: EUR
  exchangeRate: 1
  merchantCity: ROMA
  visibleTS: 1643092168637
  mcc: 5499
  mccGroup: 7
  merchantName: NATURASI'
 ...

visibleTS is 1643092168637 which converted turns out to be Tuesday 25 January 2022 06:29:28.637

maybe something has changed on the API side ?

Thanks

[markusressel]

I think the API contains two date fields, one when the transaction was created and another when it was actualy fully processed. Currently we only show one of them and never switch between the two.
Maybe we should?

[gsalvatori]

Hi @markusressel,

unfortunately I can only speak for my use case which is running a cronjob every day that gets all the transactions I've made during the day and bring them to another application. So, for me, the reference timestamp is what I can see on the app and I think it's the "created" one.

By the way, all the timestamps I get now on the dictionary returned by APIs are "wrong", in relation to what I see on the app and I'm quite sure that approximately one week ago it was working well

[tranb3r]

The app is using a new endpoint for transactions : /api/feed/v2 instead of /api/smrt/transactions.
For each transaction item in the response, there is a single timestamp field, which is the one you see in the app, and which corresponds to the visibleTS that was used before.
I think it's a pretty straightforward change to implement, but I'm no python expert...

[markusressel]

It might be possible to add support for this endpoint, but its output is pretty limited by default, contains other stuff beside transactions, and I am not sure how filtering works (the old parameters don't seem to have any effect). I think for this to be useful we would need at least some kind of working date filtering. Is there anything out there that we could build off of?

[tranb3r]

You can use /api/feed/accounts/{account_id}/transactions/search for search and filters.

Example of filter:

{
    "filterCriteria": {
        "filters": [{
                "criteria": {
                    "from": 1641942000000,
                    "to": 1643670000000
                },
                "type": "DATE_RANGE"
            }
        ]
    },
    "searchText": "amazon"
}

[markusressel]

Not sure where you get your infos from, but we need more of them if we want to get this to work 😄

Querying https://api.tech26.de/api/feed/v2 with the existing code works and returns a lot of stuff, but as commented earlier, its unclear to me what the data is constrained to. For an API we need control over that.

result = self._do_request(GET, BASE_URL_DE + f'/api/feed/v2')

Querying https://api.tech26.de/api/feed/accounts/uuid-i-got-from-accoun-info-endpoint/transactions/search gives me a 502 Bad Gateway error.

result = self.get_account_info()
account_id = result["id"]

filters = []
if from_time is not None and to_time is not None:
    filters.append(
        {
            "criteria": {
                "from": from_time,
                "to": to_time
            },
            "type": "DATE_RANGE"
        }
    )

result = self._do_request(GET, BASE_URL_DE + f'/api/feed/accounts/{account_id}/transactions/search', json={
    "filterCriteria": {
        "filters": filters
    },
    "searchText": text_filter
})

[tranb3r]

Not sure where you get your infos from, but we need more of them if we want to get this to work 😄

Inspecting the http traffic from the android app.

Querying https://api.tech26.de/api/feed/accounts/uuid-i-got-from-accoun-info-endpoint/transactions/search gives me a 502 Bad Gateway error.

It's a POST, not a GET.

[markusressel]

Still fails, now with a 500 Internal Server Error.

But I had a look at the TIMELINE output from the feed/v2 endpoint, and the dates also don't really match what I am seeing in the app or on the website. F.ex. a transaction displayed in the app as: January 31, 2022, 12:48 PM is displayed as: 1 Feb in from the API (see json below), and when interpreting the timestamp field "manually" it results in: GMT: Tuesday, February 1, 2022 5:53:23.158 PM or Your time zone: Tuesday, February 1, 2022 6:53:23.158 PM both of which are completely wrong.

{
  'id': 'redacted',
  'title': 'Steam',
  'subtitle': {
    'template': '1 Feb  ·  Online'
  },
  'tintedSubtitle': {
    'elements': [
      {
        'value': '1 Feb  ·  Online'
      }
    ]
  },
  'amount': -6.78,
  'amountStyle': 'NONE',
  'currency': 'EUR',
  'timestamp': 1643738003158,
  'type': 'TRANSACTION',
  'category': 'micro-v2-media-electronics',
  'highlight': 'NONE',
  'icon': {
    'type': 'MERCHANT',
    'url': 'https://cdn.number26.de/feed/merchants/5102.png'
  },
  'balance': {
    'title': 'Balance on {{date}}',
    'amount': redacted,
    'currency': 'EUR'
  },
  'deeplink': 'number26://main/detail/redacted',
  'gestures': {
    'swipeLeft': {
      'description': 'Pay back from a Space',
      'deeplink': 'redacted',
      'tracking': {
        'action': 'feed.gesture_swipe.left',
        'category': 'engagement',
        'property': 'payback'
      }
    }
  }
}

Not sure whats going on here, but there is probably more to it than just a different endpoint.

[tranb3r]

Timestamp issue: make sure you have all these headers properly set:

n26-timezone-identifier: Europe/Paris
x-n26-platform: android
x-n26-app-version: 3.73
n26-app-build-number: 202203000

[tranb3r]

For the 500 error: my guess is that it's either the missing headers, or something is wrong with your json content.

[markusressel]

Adding both of the x-n26 headers results in the date beeing correct when querying the feed API

"x-n26-platform": "android",
"x-n26-app-version": "3.73",

The old API does still not show the correct dates (which is not a problem if we get the new one to work).

However, even adding all 4 headers doesn't fix the POST call, still 500.
This is the json body that I sent (as in code commented earlier):

{
  "filterCriteria": {
    "filters": [
      {
        "criteria": {
          "from": 1643628699863,
          "to": 1643747219000
        },
        "type": "DATE_RANGE"
      }
    ]
  },
  "searchText": "Music"
}

Maybe the account-uuid is not the correct/same as in the old API?

[tranb3r]

The old API does still not show the correct dates

This is precisely why I suggested using the new endpoints.

However, even adding all 4 headers doesn't fix the POST call, still 500.

I don't get a 500 when sending the json content you've pasted.

Maybe the account-uuid is not the correct/same as in the old API?

Yes, it's the same. At least for me.

There must be something wrong in your headers (content-type ?)

[markusressel]

These are all the headers that I tried:

USER_AGENT = ("Mozilla/5.0 (X11; Linux x86_64) "
              "AppleWebKit/537.36 (KHTML, like Gecko) "
              "Chrome/59.0.3071.86 Safari/537.36")

_headers = {
            'Authorization': 'Bearer {}'.format(access_token),
            "n26-timezone-identifier": "Europe/Paris",
            "x-n26-platform": "android",
            "x-n26-app-version": "3.73",
            "n26-app-build-number": "202203000",
            "User-Agent": USER_AGENT,
            "Content-Type": "application/json"
        }

I also tried just the Content-Type, no luck.
If the app uses more, let me know.

[markusressel]

I also just tried the same in Hoppscotch, also doesn't work. I get the same 500 error code.

[tranb3r]

What about device-token ?