Tag Info

Hot answers tagged

4

The unofficial Winterbash inbox API If you have any user's account_id then the hats information is just one call away. And the call is http://winterbash2014.stackexchange.com/api/inbox?accountId=<account_id> For example, hats information about me can be retrieved via http://winterbash2014.stackexchange.com/api/inbox?accountId=4996787 But here ...


4

For analyzing large chunks of data, don't use the API. Use the Stack Exchange Data Explorer (SEDE), that's what it's there for. SEDE data lags real-time by 1 to 5 weeks, but that's no big problem for most statistical purposes. For intense "Big data" analysis beyond even SEDE's capabilities, use the quarterly data dumps. (Thanks, Tim Stone, for the ...


4

You can get data close-enough to "real time" for most practical purposes. See the StackHose app, for example. Read the page about the API's Throttles and Quotas. From that page we can deduce: The maximum, burst, request rate is 30 requests per second, and this risks getting your app shut down. Your app will never be allowed more than 10,000 requests per ...


3

You cannot use a standard GET request. You must obtain the access_token and then POST the necessary parameters. The steps are currently: Setup: Register your app. Link it with a post here on Stack Apps that has a legitimate [app] or [script] tag. In most cases you will also tag it with placeholder. In your app: Have the user authorize your app and ...


3

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 ...


3

Currently the API does not let you get "featured" questions (questions that have bounties) using or logic with the tag parameters. That is, you cannot search for questions that: Have a bounty AND (have Tag-A OR Tag-B) It might make sense to add a hasbounty parameter to the /search/advanced path. Workaround: In the meantime, since the number of featured ...


3

From the docs for /users/{ids}/reputation (emphasis mine): Gets a subset of the reputation changes for users in {ids}. I think you'll find that the API method you're using is working exactly as designed - it's just not designed to do what you were expecting. Fortunately, /users/{ids}/reputation-history will yield precisely what you're after. ...


2

HTTP GET $.get("https://api.stackexchange.com/2.1/posts/144890/comments/add?site=meta.stackoverflow&key=ArbQjyecuJQ((&access_token=2YVSaccesstokenomg))&body=Another%20API%20test", console.log) {"error_name": "no_method", "error_message": "this method cannot be called this way", "error_id": 404} HTTP POST ...


2

No, you cannot do this anymore via the API. API self-documentation was intentionally dropped after API version 1.1. Your only recourse is to scrape the doc pages at api.stackexchange.com/docs.


2

Reference: Stack Exchange API Authentication Looking for a beginner's tutorial to using the API Yeah the registration form now says, "Website URL is required". So, if you don't have your own website: Enter stackexchange.com as the Application Website. Enter stackexchange.com as the OAuth Domain. This will allow you to use ...


2

No. There's currently no way to do this via the API. Your only recourse, at the moment, is to scrape a user's profile page. Temporary API found, see below. The API is slow to implement features and not big on easter-eggs (that we've ever discovered anyway). If you run a /users query with all user properties enabled, you get something like: "items": [ ...


2

If you just want the total, don't bother paging through the entire full result set. Use the total property of the Common Wrapper Object. This will save lots of time and bandwidth and quota and doesn't require you to loop through the results just to count things. The total property is not enabled by default, so you will need to Create a custom filter for ...


2

It does return all the answers, but they're paged - by default you'll only get 30 at a time. You'll likely want to increase pagesize to 100, and then add the additional code necessary to make subsequent requests if has_more is set on the response wrapper. So, for example, your first request would be like ...


2

It would be simpler and more precise if you made users provide their ID number instead (for example, yours is 1637442 on Stack Overflow). Then you'd merely use the /users/{ids}/questions route to get the questions. If you really must have access by username, then: First do a search using the inname parameter of the /users route. It is recommended that ...


1

No, the API only allows you to connect to existing Stack Exchange sites, and Stack Exchange no longer sells private sites. Looks like you want one of the clones listed on Meta. Since it's not clear which, if any, of those clones offer an API, there is another approach... If you submit your site through the Area 51 proposal process and it goes to beta, ...


1

See What can I do when getting “We are no longer accepting questions/answers from this account”?. You didn't provide which site you ran the /docs/create-question post on. But, looking at your network profile, I can see that you might well be question-banned on Stack Overflow (Lots of questions with few upvotes and none of them marked answered). It's ...


1

In a nutshell and don't know ask me how to write this in C#: That first "500 error" page is normal. You must display that to the user and the user must approve. When the user approves, the page will redirect to a page (nominally stackexchange.com/oauth/login_success) with the access_token in the URL parameters. For example: ...


1

Or can I just spam them out as fast as my program can send them, as, like you said, you cache it anyway. No. The throttle discussion page specifically says: ... we consider > 30 request/sec per IP to be very abusive and thus cut the requests off very harshly. And even though the underlying data is cached for 60 seconds, the HTML requests are not. ...


1

The /search path and the /search/advanced path return only questions, not answers, and by design. It says so right in the doc pages: Searches a site for any questions which fit the given criteria. and This method returns a list of questions. Your example Stack Overflow search returned answers as well. The correct equivalent search is: ...


1

stackoverflow-java-sdk artifacts have been upload to Maven Central. Now, You simply add maven dependency in your project POM Dependency <dependency> <groupId>com.googlecode.stackexchange</groupId> <artifactId>stackoverflow-java-sdk-release</artifactId> <version>2.2.0</version> ...


1

For more information, CodeTipper has now been released for StackExchange sites.


1

This has been implemented in API version 2.2. To list the available close reasons, make a call to /questions/{id}/close/options. The result will list all valid close reasons, including pre-existing duplicate suggestions and off-topic comments. You cannot assume that a close option will be available without calling this method to see if it actually is. ...


1

See the Throttles doc page. The 10K limit is not if the customer registers, it is if you register your app and provide the key when you make API calls. Also, you can get more than 10K per IP if your app authenticates the user and then passes a valid access_token. In that case, it becomes 10K per logged in user and does not share the 10K IP limit. From ...



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