Search Results

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

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 …

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 …

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

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

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 (ha …

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

This is a classic "procedural" (or "row based" or "sequential") versus "set based" issue. See Understanding “Set based” and “Procedural” approaches in SQL or any one of thousands of similar articles. …

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

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

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

A unified call would be nice, but everything you asked for falls into one of 3 categories: It's already in the users/{ids}/associated call. It's trivially easy to calculate in the app or script. EG: …

I forget when, but sometime in the last couple of years, the /search/excerpts route started allowing is:answer in the q parameter. For example:           /2.2/search/excerpts?&q=Hear! is:answer&sit …

You can get this data easily by scraping or by using the websocket interface that Stack Exchange helpfully leaves available. If you are making an application or webpage, just fetch stackoverflow.com/ …

Until the feature request is approved (unlikely, and a similar request has no developer love either), you can get this number in one of 3 ways: You can get slightly stale data with this SEDE query ( …