6
You can create and edit filters from the documentation page of the API endpoint.
So you start at the Index of all endpoints. There you'll find /users/{id}/answers.
On the right at the top of the parameter block you'll find the filter dialog:
When you click the [edit] link the filter dialog opens:
Where you can expand any the [types] provided by this ...
5
This is a bug. The timeline path seems to have several problems. More on these below.
The earlier date query returns the result you expect, but look at it in the document explorer:
Notice that the entry is a comment and that it has an Owning post.
Now if we look at the whole timeline (filtering out some user cruft), we see:
Just two revision entries for ...
5
First of all, I'm guessing the HTTP 400 errors are directly related to the fact that you are transmitting the access_token over standard HTTP instead of HTTPS. The API (if I remember correctly) throws an error if you try to pass an access token over standard HTTP and immediately invalidates the token.
You actually don't need to include an access_token to ...
4
backoff isn't used to indicate when you're breaking api limits (we start returning errors when you break contracts).
The typical cause of a backoff is a request that takes unusual resources to run. These are normally either complicated queries or high page values; however, backoff is applied dynamically so the exact definition of "complicated" and "high" ...
4
That is the 2.1 documentation, it's just the title (and perhaps the first sentence) that hasn't been updated.
All of the routes added in 2.1 are there, so you don't have to worry that it's missing anything important.
4
The user_id is the per-site user id (in the above case, for Stack Overflow). The account_id is the global Stack Exchange account id (i.e. the id of your Stack Exchange account).
The account_id is probably the best key if you're looking for a global identifier, since the individual per-site user ids will be different on each site the account is associated ...
3
Update: Op followed the advice, below, and changed the question from a bug to a feature-request.
This is not really a bug. Right at the top of the API documentation, it states that the API is read-only, in bold letters:
Stack Exchange API v2.0
This is the documentation for the v2.0 read-only (with optional authentication) Stack Exchange API. If ...
3
Assuming you're talking about these numbers for a particular user, you can use the /users/{id}/associated route with the given user's network ID to get these values for each of the sites the user is a member of.
You can selectively filter through the results to pick out the sites that you're interested in.
2
This was fixed in the latest deploy, there was a problem selecting the most recent notice for post with multiple notices (which is rare).
2
migrated is equivalent to searching with migrated:1 or migrated:0 on the site itself.
In other words, migrated=true returns questions that have migrated_to (questions that have been migrated away from the site they were originally asked on). migrated=false returns questions that don't have migrated_to, but may have migrated_from.
There was a bug (fixed in ...
2
This has been fixed in the latest deploy (it also affected body turns out).
We've got some changes to our search infrastructure in the pipeline, and API v2.1 is being used to test them out. You might have noticed it's had some... issues. Better to find them in an API beta than after the rollout to the Q&A sites though.
2
The little sidebar block will refer to API V2.1 starting with the next build.
2
This was fixed in the latest deploy.
The bug was basically selecting the wrong date to display (in this case, an associated post), and the right date for filtering and what not. Since not all badges are associated with a post, not all displayed dates were set and when they were set they were off by some (basically random) amount.
2
This would be a two-step process if the /posts/{ids} path returned title, but it doesn't. Since the /answers/{ids} path, does return title (with an optional filter setting), then it should be easy-ish for /posts/{ids} to do so as well. Perhaps this would be a good feature request?
Anyway, as it stands now, you must do this in pages and in 3 steps per page....
2
Grouping the API documentation by type gives you the list of routes under the specific object type that they return, with a link describing the respective type. You should be able to determine the comprehensive list from that.
2
Update: As of api-v2.2, it's also possible to write questions and answers via the API.
There are at least a few examples in use, of API 2.1 apps, that write comments. See:
The Quick Media Solutions app
The StackX Android app
The SX.el Emacs app
Re:
Am I correct in thinking that only comments can be written and not questions?
Yes, that's correct. ...
2
This was fixed in the latest deploy.
Sorry about the wait, a fix was actually staged a few days ago but deploying it was delayed by our yearly company get together.
2
This was fixed in the latest deploy.
Root cause: I had let a copy of our JSON serializer (currently ServiceStack.Text) get out of date.
1
never mind, I found the answer, https://stackapps.com/apps/oauth/
1
The documentation says about private_info:
access full history of a user's private actions on the site.
What this means right now (API 2.1) is that that scope is needed to use the /reputation-history/ paths:
Discussion (of /users/{id}/reputation-history/full)
Returns a user's full reputation history, including private events.
This method requires an ...
1
The code in question was not generated by Stack Exchange. It was generated by a user.
So, yes, quite often, the HTML (and all other code samples generated by users) will be malformed.
However, in this case, note that <li> tags are not required to have closing tags. I agree that it is bad form to leave them off, though.
1
As described in the /me/inbox documentation, the route is
...effectively an alias for /inbox. It is provided for consumers who make strong assumptions about operating within the context of a single site rather than the Stack Exchange network as a whole.
Since it's just more or less a convenience route for the global /inbox method, it doesn't actual ...
1
Tricky, this was complication of date rounding (we store dates with sub-second precision in the DB) and some bad math when converting unix epoch dates for certain routes.
The latest build should fix these bugs.
1
Use the /questions path and sort by: creation, desc.
For example:
/2.1/questions?pagesize=15&order=desc&sort=creation&tagged=php&site=stackoverflow
1
Fixing WebBrowser Control
I also had the issue of the WebBrowser control handing when trying to login.
Although requesting a token in IE (11) works, I found that IE itself also hangs when I put it in IE 7 emulation mode. This suggested to me that my previous attempt to make the WebBrowser control use a newer version had failed.
I found this article, Web ...
1
This will be fixed in the next build.
1
Notifications typically contain links within their bodies. They're considerably more free-form than inbox_items, in that they're not typically attached to a post.
Notifications only even have directly attached posts (at time of writing) in the bounty and edit cases.
Note that if there's a post_id present, you can query /posts/{ids} to get a link. ...
1
This was a caching bug actually, a few parameters weren't being considered when doing a cache lookup (such as views) so you'd get back non-sense data.
It's been fixed in the latest deploy.
Only top voted, non community-wiki answers of a minimum length are eligible
