10

While this is not available I don't think SE can do much to prevent it. I don't have any easily readable code to give you code example, but the theory is following: The upload request: To upload images to Stack Exchange, you must send following POST request to https://__HOST__/upload/image: fkey: we'll talk about this token later source: web/computer ...


8

I don't see any particular reason not to add it, but there are some workarounds you can use in the meantime: Build a cache of all site information with the site URL as the key, and then look up the api_site_parameter value (and associated information) that way. or Use the fact that the domain name can be passed as a valid value for the site parameter, in ...


7

I'll slot this in for v2.1, not super useful in general but definitely interesting information that we should make available.


7

Whelp, that was an oversight. accept_rate should now be returned on both user and shallow_user. Note that when insufficient data is available to calculate an accept rate, we don't return anything at all. The exact rules for calculating accept rate are subject to change, but currently documented here. The API returned accept rate should always match the ...


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


7

Should we ask the dev team politely to enable Stack Snippets here? Yes! It would, primarily, be useful in cases such as your example: support with using the API. I think people looking for help would always appreciate a minimal example, just to see outputs and how you might go about doing something, and it doesn't take too long to make a snippet! But it ...


6

For /sites (and only it) I have removed the pagesize constraint. I believe in this case it makes sense, since applications are expected to query all of that data and cache it for long periods of time. The constraint remains elsewhere, as it's very important for performance reasons.


6

API V2 did this, we send down: Access-Control-Allow-Credentials: false Access-Control-Allow-Methods: GET, POST Access-Control-Allow-Origin: * With every response.


6

Actually this can be done with using the rss feed channel on ifttt. together with the rss feed from the Stack2rss app that transforms stackoverflow api queries to an rss feed. like: http://stack2rss.stackexchange.com/stackoverflow/users/{{your user id}}/questions?body=true you should check the api for the specific query you like (respone, specific ...


6

You cannot get the days visited, nor consecutive, information for a user because that is private information(Poster is SE representative). Stack Exchange is supposed to be about the content, not the people. And knowing people's (more detailed) visit history is a social metric, not an on-topic bit of information. In a similar question, one power-user put it ...


5

the original question was apparently for V1. in V2 we now have https://api.stackexchange.com/docs/required-tags the request: https://api.stackexchange.com/2.0/tags/required?order=desc&sort=popular&site=stackapps will return required tags


5

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

When this class of error is encountered, the number of seconds until the quota rolls over is indicated as part of error_message now. For example: { "error_message": "too many requests from this app/user pair, more requests available in 76400 seconds" } This is meant for debugging and development purposes only, applications should take care to not actually ...


4

There are 2 ways to get the 10 most recent questions of a tag, either on the /questions method or /search method. The parameters on both routes are the same, just set tagged to your tag (eg iphone), and sort to creation, and order to desc So that's either: https://api.stackexchange.com/2.0/questions?order=desc&sort=creation&tagged=iphone&site=...


4

I don't follow, for date times the most recent date is the largest date. Sample return by events { "event_type": "question_posted", "event_id": 9369546, "creation_date": 1329777738 }, { "event_type": "comment_posted", "event_id": 11832402, "creation_date": 1329777736 } 1329777738 => Mon, 20 Feb 2012 22:42:18 GMT 1329777736 => Mon, 20 Feb 2012 ...


4

If this doesn't happen, this simple script will do it for you!: $('.site-picker.ui-autocomplete-input').on('input', function() { setTimeout(function() { var mylist = $('body > ul.ui-autocomplete'); var listitems = mylist.children('li').get(); listitems.sort(function(a, b) { return $(a).text().toUpperCase()....


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

Note that version 2.3 has been around since at least Aug 28, 2015 (Date of that answer). I could have sworn that one of the SE guys said they weren't going to document it, but can't find a reference for that. Anyway, in Jan 2017 the (former) API developer, Brian Nickel, said: There's no timeline yet for new features (and API backing them), just focused ...


4

Yes, you can find out if the user has received the association bonus using the API. It's a bit clunky though. However, as we discovered, "association bonus rights" are rather meaningless at the moment. Otherwise, you'd be able to edit wikis, upvote, comment, and flag on Information Security Stack Exchange right now, despite currently only having 1 rep ...


3

There is an /events route that: "Returns a stream of events that have occurred on the site." Greg Hewgill has created a firehose JSON streaming event service which closely mimics the Twitter Streaming API. He has also created a page to demo the service here: StackHose: live real-time event stream in your browser


3

If you visit: http://stackapps.com/edit-tag-wiki/codeigniter ... you're redirected to that URL. If you don't mind the redirect, you might just be able to get around it that way. As far as I know, there's no documentation about when you can specify a name versus when you must specify an ID number, and I know of no API route that returns the ID numbers. ...


3

i have a doc scraper that produces json schema and smd. eventually it will be published as a service on SOAPI2.com, much the same way that soapi.info provides meta for v1. but until then you can find the meta files here: https://github.com/bitpusher/SOAPI2/tree/master/src/SOAPI2.DocScraper/js this meta is what i generate routes and model for soapi2 from, ...


3

Categories aren't sufficiently stable to expose in the API. It is entirely possible (even likely, in my opinion) that we'll revisit and rework the proposal categorization significantly in the coming year.


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

While not perfect, some of what you're looking for is currently available. The bounty owner user ID and custom message will be in the results if you supply a filter that returns question.notice, since the notice visible during the bounty should be the one associated with the bountying user. This won't give you the high-level bounty reason though, and if ...


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

If you already have a token, then you can use the /me/associated network route to get the associated site for the authorized user. There's a similar route that takes a network account ID and does not require an active access token.


3

Currently, the Stack Exchange API has nothing to do with Stack Overflow Careers. Anyway, there is no API for accessing Stack Overflow Careers job listings. Best you can do is grab the most recent 1000 listings from the Careers "all new jobs" RSS feed.


3

This is very costly to do in the API and currently impossible for many combinations of tag and date (because it would require more than the 10,000 allowed API calls per day). I'll write more about that tomorrow (11/11 or 11/12 UTC). Meanwhile, perhaps a SEDE query will work? The query: Top Answerers, by your tags and your date range takes your date range ...


3

The official documentation is here: Available flags vary from object to object, user to user, and site to site. An application should not assume that particular flags are always available, or that particular option_ids are stable. Which isn't great. You may be able to get away with it, but there's nothing saying the option IDs can't change out from under ...


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