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

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

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

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

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


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

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

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

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

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


3

Updated thanks to comments by Brock Adams and user43888. There are two methods to achieve this: Method 1: inefficient, but future-proof as it only depends on the SE API. Query the SE API for all Meta.SE users, in groups of 100 (maximum allowed ID) Get an access token and an API key, to be able to run the above call nearly 4000 times (equivalent to the ...


3

It's not possible (short of fetching all users and filtering yourself). The API simply does not offer that query. For alternatives, see the Data Explorer (SEDE): https://meta.stackexchange.com/q/253728/295232


2

The URL in the link field is sufficient to uniquely identify an inbox message. Each kind of notification has a different format of URL, and you only get one inbox notification per event.


2

Hear! Hear! I want to study what makes a good answer on SO. I started by querying complete web pages (questions with all comments, answers, and their comments) for questions with some minimum score (such as 5) for a number of fixed tags A,B,C created in some time period (say, one full week two months ago). This can be done well with \search and a filter that ...


2

Whilst an API method would be so much more helpful, and easy to use, the mobile apps use the URL http://stackexchange.com/hot-questions-for-mobile. You can send a GET request to that URL and parse it easily because it's in JSON format. It's an array of objects, eg: [ { "site":"codegolf.stackexchange.com", "question_id":91182, "...


2

The problem with this isn't so much the security (though that's a concern), it's that we don't want the backwards compatibility constraints such blessed installations imply on our HTML and javascript. As such we're unlikely to ever do something like this, so I'm status-declined-ing it.


2

The API allows you to get question data based on ID, so since all forms of question URLs for Stack Exchange sites have an ID in them, you can pull that value out and pass it to the /questions/{ids} route. Likewise, if you don't know the specific site in advance, you can pull out the hostname and pass that in dynamically. As an example, I parse out similar ...


2

UPDATE: The feature appears to be present in the, so far, undocumented API version 2.3. See captncraig's answer on this page. After all these years, it looks like this might never get implemented. However, it's not too hard to get the information via page scraping. From a browser or scraper that is logged in as the user, fetch the site's question page. ...


2

There is no app, exactly like that but two are pretty close (they don't have any annoying sounds). These both run on Windows + Linux platforms and provide desktop alerts for favorited/tracked tags. Check out: StackApplet: , built on the QT framework New Q!: , Uses the Chrome browser for its engine.


2

You already know the site, it has to be built in to every /questions query. But, if you are querying separate sites with concurrent AJAX queries, merely encapsulate the site name in your AJAX callback. See this Stack Overflow question for an example of doing that in javascript. Alternatively, you can parse the link property of the question response to ...


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