7

This is currently not possible via the API. The best you could do is have the user logged into a browser and then screen-scrape the stackoverflow.com/users/{user_id}/?tab=votes pages... Hardly an acceptable workaround. The Authentication doc, Scope section, does say: private_info - access full history of a user's private actions on the site. But ...


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

This will be fixed in the next build.


3

The key mistake here is neglecting the Wrapper Object, and this is a big flaw with the filter documentation. The wrapper is the box that everything you get from the API comes in. You always get the wrapper object except in the grossest of server/API errors. (In your case you were getting a wrapper of {}.) The stuff you care about, the payload, is the ...


3

The date is in "Unix epoch time", as described in the API-docs, Date Formats section. How you do the conversion depends on what language you are coding in. Here's one way in javascript: function unixEpochTime_TO_Date_DDMMYY (unixEpochTime, returnUTC) { var year, month, day; var dateObj = new Date (unixEpochTime * 1000); if (returnUTC) { ...


3

The payload seems to be limited to 3000 characters by the Stack Exchange engine itself: However, the actual field returned by the API may be longer, as the user's 3000, markdown characters are expanded into HTML. As stated in "Can we have maximum length of string in API help pages?", the API itself enforces no length limits on the data and... we're not ...


2

This was fixed in the latest deploy.


2

The /me/associated routeDoc is the preferred way to turn an access_token into a list of users, it returns the collection of per-site user details that can be quickly fetched. It's basically the user's account tab. If you need more details about a user on a give site, then turn around and hit /me (or /users/{ids}) on the sites you've discovered via /me/...


2

/questions take's a semi-colon delimited list of tags in the tagged parameter. If tagged is set, questions returned will have all the passed tags (ie. it's an AND operator). https://api.stackexchange.com/docs/questions#order=desc&sort=votes&tagged=python&filter=default&site=stackoverflow&run=true ^ for example, that query returns all ...


2

See the documentation for the /questions path and the question object spec. To get answers, merely use the /questions path with a filter that has answers enabled. To get the latest 30 questions, sort by activity, descending, and request only the first page with a page-size of 30. For example: /2.1/questions?page=1&pagesize=30&order=desc&sort=...


2

I found the answer. On the documentation page we find all needed information: Example: /2.1/questions? pagesize=50 fromdate=1371859200 todate=1372550400 order=desc sort=votes tagged=javascript site=stackoverflow https://api.stackexchange.com/2.1/questions?pagesize=50&fromdate=1371859200&todate=1372550400&order=desc&sort=votes&...


2

This was fixed in the latest deploy.


1

The tagged parameter to /search and related methods is an OR. This query will return questions tagged c# or java, for example. Or is rather expensive, which is one (of the many) reasons those methods are limited in how many results they return.


1

You would use the inname parameter of the users path. For example this gets users with marcamillion in their name, on Stack Overflow. Note that the filter parameter controls what fields are returned, not the content of those fields. I don't use Serel (or much Ruby), but the syntax is probably: Serel::User.inname('marcamillion').get Or, with some more ...


1

For one use the current API version (2.1) instead of an old one (1.1 in your case). Furthermore, when using JSONP you do not have to parse the result. The data object you get in your success method already is a JavaScript object you can work with. $(function(){ $.ajax({ url: 'http://api.stackexchange.com/2.1/search?page=1&pagesize=15&tagged=...


1

The API expects JSONP requests to specify the callback as the jsonp parameter, not the callback that jQuery uses by default. While really you should consider upgrading to API 2.1, which does expect callback (and allows CORS, for that matter), you can fix your code by putting in the jsonp parameter placeholder: $.ajax({ url:'http://api.stackoverflow....


1

This was dropped intentionally. The problem is that maintaining this sort of meta-api is both intensive (lots of v1.1 was spent not breaking v1.0 because of the way introspection was working) and of very little utility. Yes, it's useful for generating wrappers; but those wrappers are written once per version, and not updated meaningfully. If we were ...


1

By definition all /search and /similar queries are made on one specific site. There is currently no way to search more than one site. Example: http://api.stackoverflow.com/1.1/search?intitle=linq This example will search only Stack Overflow for the term linq.


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