Return to Answer

This evening, after being inspired by How to get (unread) achievements?, I did some analysis with mitmproxy. It turns out that the Stack Exchange mobile apps use an undocumented API v2.3 method for this: /me/achievements.

One evening, after being inspired by How to get (unread) achievements?, I did some analysis with mitmproxy. This was at a time that the publicly released version of the API was 2.2; it turned out that the Stack Exchange mobile apps use a (then) undocumented API v2.3 method for this: /me/achievements.

This evening, I did some analysis with mitmproxy. It turns out that the Stack Exchange mobile apps use an undocumented API v2.3 method for this: /me/achievements.

This evening, after being inspired by How to get (unread) achievements?, I did some analysis with mitmproxy. It turns out that the Stack Exchange mobile apps use an undocumented API v2.3 method for this: /me/achievements.

There's a related GET call to https://mobile.stackexchange.com/1/push/topbar-counts which returns the number of unread inbox items and the total new reputation (the green +x badge), but it only works with a token which belongs to the mobile apps. It returns something like this:

There's a related GET call to https://mobile.stackexchange.com/1/push/topbar-counts?filter=vqc7J which returns the number of unread inbox items and the total new reputation (the green +x badge), but it only works with a token which belongs to the mobile apps. It returns something like this:

The filter seems to be necessary; without it, I get a backoff response.