Hot answers tagged

4

The routes that don't link require POST requests because they create context, so there's nothing meaningful to be gained by going to those URLs in your browser. The rest of the routes return data when you send GET requests to them, which is why the link is useful in that case.


4

items is documented in the Common Wrapper Object. It is an array of whichever object the given route returns. In the case of /me/associated,  items is an array of network_user objects. If you use a filter that returns .wrapper.type, then type will return the type that items has assumed. EG: { "items": [ // <=== Linked ...


3

If this doesn't happen, this simple script will do it for you!: $('.site-picker.ui-autocomplete-input').on('input', function() { setTimeout(function() { var mylist = $('body > ul.ui-autocomplete'); var listitems = mylist.children('li').get(); listitems.sort(function(a, b) { return ...


2

This sure looks like a bug. Site search shows that there were 946 browserify questions created in 2015 (so far). The /tags route doesn't have a created option, but it shows 0 questions were active in 2015! No permutation yielded valid results when trying to specify any fromdate after 2012-05-23 (midnight on the 22nd). It seems the result is either the ...


2

Yes, if you omit those parameters it will give you the expected result... If a valid token is passed, then it will return the user ("There can be only one.") who obtained/approved that token. For this route, the fromdate and todate parameters filter on the creation_date property of the user object. So, if the authorized user signed up for his/her account ...


2

RE: Is site the api_site_parameter of the site object? Yes.   Although as stated in the "Per-Site Methods" section of the main doc page, you can also use the full domain name, EG cooking.stackexchange.com. No, user and shallow_user are site specific objects. You absolutely need to specify site to get these. Supposedly, the assumption is that all ...


2

This is exactly how it should be (except that the doc page might be more explicit). The meta_site parameter refers to Per-site Metas. Meta Stack Exchange is not a per-site meta. Think of it as a Stack Exchange main site about Stack Exchange itself -- encompassing Stack exchange operations and hundreds of SE-operated sites. See "The future of ...


2

This is a very minor bug in the documentation page. The online doc page adds a convenient hyperlink to the post (The link part is not in the API's JSON response). That's a good thing. Most of the time this is rock solid, but notifications span all Stack exchange sites and the API doc pages normally only expect one site at a time. When the page is making ...


2

There is no difference and... The inbox has always been "The global inbox". Certainly for as long as the API has existed. So any inbox route will be Stack Exchange wide, even if it accepts a site parameter. If you look at the doc for the /users/{id}/inbox/unread route, it says: This method is effectively an alias for /inbox/unread. It is provided for ...



Only top voted, non community-wiki answers of a minimum length are eligible