Search Results

It seems that the /users/{id}/timeline route is returning an incorrect total. For example, the following URL is reporting a total of 1607 items: http://api.stackapps.com/1.1/users/7789/timeline …

After reading the docs/faqs, I couldn't help but wonder... What exactly is a day? When does it start? When does it end? What timezone are you using? In other words, when my app runs out of reques …

I already tried this. Complete exasperation with sending POST requests to StackOverflow - Meta Stack Exchange. So it's v2.0 or nothing.

Given a user's email, it would be great if we could hash it and search for that user with it. The reason for this is suppose: Someone has a website On that website, they invite SO users to enter th …

For example, to display a user's profile, the following routes are hit (keep in mind that these requests are all made to display one page): http://api.{SITE}.com/1.1/users/{ID} http://api. … sort=votes&pagesize=5 http://api.{SITE}.com/1.1/users/{ID}/answers?sort=votes&pagesize=5 http://api.{SITE}.com/1.1/users/{ID}/badges http://api. …

First of all, version 1.1 of the API has been deprecated for quite some time now. Users are strongly encouraged to move their applications over to version 2.1. … Version 2.0 of the API introduced the concept of filters, which (in your case) requires that you manually specify that you would like to fetch the post body. …

You can find the page listing all of your v2.0 and v2.1 keys here: https://stackapps.com/apps/oauth

As of version 2.0 of the API, answers can return a link field in the response, which can be returned in the response by creating a filter that includes it: …

This will provide you with an API key and application ID. If you want the application to use the implicit OAuth flow, then make sure the "Enable Client Side OAuth Flow" checkbox is checked: …

"I'm also interested in looking how any Stack Exchange API frameworks might have already implemented methods to query all pages in such "friendly" ways." … I wrote a PHP wrapper for the API that does this in a rather unique way. …

You can find more information on this page in the API docs: This affects "shallow user" fields most frequently. For example, this question's owner has been deleted (a very rare occurrence). … An API query for that question returns no user accordingly. …

A possible solution to this finally hit me out of the blue like a ton of bricks: Instead of retrieving successive pages by page number, why not retrieve them by date range? Here is a quick rundown of …

Its behavior is designed to match the actual API route as much as possible. That being said, it serves mostly as a demonstration that such a thing is possible. … (Not only that, but it actually uses the real API to keep the information up to date.) …

You can do this by making a JSONP request. This works by returning the results of a query in a <script> tag that invokes a callback. You can find more information about it here.

Here is a summary: activity - sort by recent activity (edits, answers, etc.) - when using order=desc the first questions will be the ones with the most recent activity. votes - sort by vote count - …