13

Funny story... When I first joined the team here at Stack Exchange, Jeff just went around on the trilogy sites and made me a moderator... And he used the "elected" route instead of the "appointed" route, for reasons that are no doubt lost to time (or maybe they're preserved in chat, I can't be bothered to search). This problem shows up on Super User and ...


7

No. Currently the users type does not return any private_info and neither does the user_timeline type return any voting information. No other API method allows for detecting a user's vote history except one question at a time. You would have to fetch every single question and test the downvoted and the upvoted properties. If you limited your search ...


7

Confirmed; see bottom section, below. However, please refer to Provide a way to retrieve questions and answers that have been deleted -- which is "status-planned". This is a feature, not a bug. And this kind of feature has been requested many times. So, shush please, don't ruin it for us. ;) Confirmation info: You can see this behavior (for now) with this ...


6

Yes, that bug is annoying, especially since specifying a todate that's before the fromdate returns a valid result set, EG: { "items": [], "has_more": false, "quota_max": 10000, "quota_remaining": 9995 } -- rather than an error. Having the dates be equal is theoretically possible. Having negative time is impossible (in this context). However, ...


6

After re-investigating my code, I realized what was going on here. For this particular project I wasn't using the API key and access token of my own application; I'm using the ones I sniffed from the communication between the Stack Exchange mobile app and the API. The Stack Exchange mobile app has an unlimited quota, it seems.


5

Nope. Neither the user_timeline object, nor the user object return any flagging information, at all. (as of API version 2.2). The question, answer, and comment objects can return a can_flag boolean, but this does not necessarily indicate that the user has already flagged, and it returns false for a variety of reasons. Flagging history is especially ...


5

Confirmed the bug on a post that accrues comments much slower than a typical Stack Overflow question does. Currently, the OP's filter returns "comment_count": 1 on that post. There are no comments. I believe this is a side-effect/bug/quirk with how the API appears to be counting the comments. ¿Perhaps it is counting Ids in the comment table and not ...


5

To get the questions in a tag you can simply use the /questions endpoint as that does accept a tagged query parameter, from that document page: To constrain questions returned to those with a set of tags, use the tagged parameter with a semi-colon delimited list of tags. This is an and contraint ... The API endpoints can relatively simple be used from ...


5

I don't know for sure what the original problem was, but the most recent issue was a result of implementing a new badge without rebuilding the API. Once the API was pushed to production, the bug was resolved. If it happens again (especially if there's a new badge) please let me (or really any employee) know. We can contact a developer directly. From a ...


4

Use the /users/{ids} route to get account_id. Then pass the account_id to /users/{ids}/associated. Note that account_id is exactly the kind of information that should be heavily cached by your script/app. (Hint, hint; wink, wink; nudge, nudge. (^_^) ) For example: /2.2/users/10349?site=superuser&filter=!T6o*9deY.2ZD3-(n4f Returns: { "account_id": ...


4

This is not possible in api-2.2, but it might be made available in 2.3. Semi-source: I had an email exchange with someone from the android app team, who then talked to the api team. It's not on 2.2 but they're "open to moving it to the 2.3 API release".


4

I mean, the value's not wrong, just perhaps not useful? The QPM is taken over the entire lifetime of the site, so 10005086 / 3644369.9112 = 2.745354133577943, where 3644369.9112 is ((Date.now() / 1000) - site.launch_date) / 60 I'm not sure if there'd be a better default timespan though—it's probably better to just pull the question count for the period you'...


4

You are using the "Javascript SDK" and that's not how it works. The doc page calls the SDK "small and minimalistic".   The source code states: This file is provided to API clients to automate various tasks, initially focused on login. In fact the SDK really only does one thing. It helps you get an access_token if you need to authenticate. It ...


4

The original intent of these options is clearly not to enable automated flagging, but rather to allow an application to generate a UI that presents the applicable options to a user who would be expected to understand them. With that in mind, the only safe way to identify a flag is by using an exact string match: one that takes into account the terms used ...


4

It's probably because the referenced post has been deleted. The API excludes (most) deleted data (usually).


3

Of course as soon as I finally break down and ask a question I see my mistake: Applications that have the client side flow enabled can use https://stackexchange.com/oauth/login_success as their redirect_uri by default. I had "Desktop OAuth Redirect Uri" disabled which the javascript SDK uses. (Note the url posted in the question) Leaving this up here in ...


3

An inbox message body is not the same as a post body. Inbox messages are truncated by design. Here's a snippet of my inbox: Notice how the "body" is truncated at 100 characters? (Counting the ... and accounting for HTML entities like '.) The results I get from /2.2/me/inbox?filter=!SmOhH2b13NujlyyXX6 are exactly the same: "body": "Very good....


3

There really is no particularly satisfactory way to do this since all versions of last_activity_date conflate a question's activity with the activity of its answers. You are going to have to fetch lots of items and filter out the chaff yourself. There are 2 main routes you can take, events or questions: A) Use the /events route: Use a filter that ...


3

This is a bug. I've tagged your question accordingly. total, in the wrapper object, should always be the length of the items array, after concatenating all pages of results. When I run /2.2/notifications?pagesize=100&filter=!*L6X1NqVdlFobvlv, I get 4 pages of results, currently totaling 382 items: total remains fixed at 77. This is clearly a bug, ...


3

Although it doesn't appear to say so in the doc page, intitle expects an exact phrase, not a list of words. You can currently see this by: /2.2/search?intitle=get column array&site=stackoverflow which currently returns one result with that exact phrase in the title, but doesn't return the many questions that have those 3 words in other arrangements. ...


3

Yes, calls to /access-tokens/{accessTokens} use API quota. You can see that by repeatedly running /2.2/access-tokens/XBWL0stf*YIOCl7WpJHqYA)) for example. With each call, the quota_remaining value will decrease. However, there is no reason that the token check has to use the same key as your main app. The token check and your main app would then use ...


3

You got that error because you set the OAuth Domain like example.com:8080, not the redirect_uri. That's not how you configure non-standard ports; see below. The redirect uri, with port, feature now works (it didn't once upon a time). To use, adjust your app settings: Go to https://stackapps.com/apps/oauth and click on your desired app. Click the "Edit ...


3

It's a bit confusing but that is not a bug. Think of it as, "Reputation change from when to when?" Since you specified neither a fromdate, nor a todate, you are effectively asking for the changes for all time. If you run the query for Nov 1, 2015 to Nov 9, 2015:           /2.2/users/21539/reputation?fromdate=1446336000&todate=...


3

This appears to be closely related to the bug: Why is comment_count=1 (incorrectly) when this particular filter is used?. The workaround from there -- altering the filter by: selecting comment.comment_id and selecting question.comments appears to work in this case too. (Although, in at least one instance, it seemed to need question_id as well. But this ...


3

Turns out this is completely my fault :/ I overlooked the expiry aspect of the access token which meant that I got the default 86399 seconds (~24 hours), which meant my users had to get a new access token every day. Because this is a userscript which is used daily, it makes sense to have a no_expiry scope so that the user doesn't have to repeatedly ...


3

This is a bug and seems (based on a series of A/B tests) to be linked with the body_markdown property. That is, if your filter returns the tags array, it works: "items": [ { "tags": [ "batch-file", "cmd" ], "answer_id": 42292030 }, { "tags": [ "ios", "arrays", "swift" ], "answer_id": 42295110 }, etc... , unless body_markdown is also ...


3

Your app is subject to IP throttling as explained in the rate limiting documentation: Every application is subject to an IP based concurrent request throttle. If a single IP is making more than 30 requests a second, new requests will be dropped. The exact ban period is subject to change, but will be on the order of 30 seconds to a few minutes typically. ...


3

No, you can't get the access_token in the query/search part of the URL. This would be a security leak that would allow 3rd parties to see your access_tokens on the web. Reference: OAuth2.0 Implicit Grant flow. Why use url hash fragments? RFC 6749 If your app is running on a server, use the explicit OAuth flow. This returns a one-time code to your server -...


3

The link is correct. The purpose of that control is to provide a URL to the doc page with all the parameters prefilled. This is what most users expect and is similar to how that link control works on the rest of Stack Exchange. To get a direct link to the API, click on the link next to the Run button: This has a URL like: https://api.stackexchange.com/2....


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