I have a script which I use, based on the StackExchange API, to regularly download a local backup of various questions relevant to me (the ones I've asked, answered, or favorited) across various SE sites. Recently I noticed that this script stopped downloading favorites. And indeed, the URL https://api.stackexchange.com/2.2/users/17064/favorites?sort=activity&order=asc&site=mathoverflow&filter=bYJ_Djhc_U%29oHdva4ija%29v&min=1661983200 now returns an empty list.

I suppose this is due to bookmarks having been renamed to “saves”, but this doesn't tell me how to actually use this feature programmatically. The API documentation says nothing about favorites being deprecated, nor does it provide a hint as to what the replacement method is or anything of the sort.

So, is there some way I can get something equivalent to the old behavior except by scraping the HTML from https://mathoverflow.net/users/saves/17064?sort=activity which is precisely what I wanted to avoid by using the API?

(Note that I'm fine with a solution that would involve, for example, re-migrating my “saves” to bookmarks if that's in any way possible. I have no objection to them being publicly visible, for example.)

  • 1
    Part of the change is making it private, we can no longer see what other people Save. Commented Oct 18, 2022 at 15:41
  • 1
    @ShadowTheKidWizard Yes, I'm fine with either providing an access token or somehow making my saved list public. I don't care wither way. But my question is: is there an API method which will work?
    – Gro-Tsen
    Commented Oct 18, 2022 at 15:42
  • 1
    This I don't know, but my educated guess is there isn't, they still didn't reach this stage, and removed it from the API due to Saves being private. Commented Oct 18, 2022 at 15:46
  • 6
    (BTW, this was already asked here, without official response.) Commented Oct 18, 2022 at 15:48

1 Answer 1


As part of the Saves launch, I failed to communicate anything about the API in the FAQ section of the launch announcement post, however we have tickets created to do some investigation of the current API usage and determine what steps we need to take to either support the existing features (i.e. saved questions but only for your account) and/or potentially creating a new set of APIs for Saves. Once we have a plan finalized, we will communicate back to Meta.

  • 5
    "Once we have a plan finalized" - something tells me it's going to take a very long time. :( Commented Jan 11, 2023 at 15:00
  • 3
    And of course I'm correct, sadly. One of those times I don't like being correct. Commented Aug 6, 2023 at 13:14
  • @ShadowWizard Unfortunately, you're apparently still correct. ;) Commented Jun 11 at 9:14
  • 1
    @EndAntisemiticHate true, and this is just another proof of the total lack of communication between Stack Exchange and its users. The users ask stuff, and get ignored. Worse, they get false hopes like this one, that things are looked at, while they are not. And those are the most annoying things, and the reason I no longer upvote staff response even it appears to be positive, like this one. Too big a risk it's just a false hope. :( Commented Jun 12 at 18:30
  • @ShadowWizard I understand where you're coming from. It's unfortunate that for a site based on human communication, Stack Exchange management is so bad at effective communication. I still upvote because I want to be a positive influence (and show that we are interested in communication). Of course, IIRC, you're a positive influence in many ways too (IMO). Commented Jun 13 at 4:49

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .