Tag Info

Hot answers tagged

6

Most routes that take an ID, including the /users route, will accept multiple values separated by semicolons. For example, a query like /users/1%3B22656?site=stackoverflow will give you results for both user 1 and user 22656. You can combine up to 100 ids in this fashion.


5

By "bio" you mean the about me field, right? ... Any path that returns a user object will return the about_me property, but this is not returned by default. You have to use a filter that has about_me enabled. For example, here is a query to get your "About me" on stackapps: users-by-ids#ids=8109&filter=!.2mo6GlnpFPFeBKnaz&site=stackapps An ...


5

Actually, I think I figured out a way to do this. If you specify the following: /users?filter=john&sort=name&min=john&max=JOHN That is, sort by name with "min" and "max" both set to "john" then it returns only those people whose name is exactly John. I wonder whether this efficient for the backend to process? It seems to respond pretty ...


4

Given that the API is not connected to your user account in any way, I don't see how it would...


3

Querying Stack Exchange Users You may leverage the Filtering and Sorting capabilities of the Ajax grid to shape results based upon the entire Stack Exchange user base. You may export the contents of the current grid page to CSV.


3

Liking it so far. Here are some ideas. No idea how practical they are. I'd really like a page which could tell me the latest activity of all my favourite users, maybe with a clever filter to remove the uninteresting stuff (badges, edits, accepts). My browser just popped up a window for a fraction of a second. Please tell me that wasn't you... Note that ...


3

No. Currently the users type does not return any private_info and neither does the user_timeline type return any voting information. No other API method allows for detecting a user's vote history except one question at a time. You would have to fetch every single question and test the downvoted and the upvoted properties. If you limited your search ...


2

Not that this will solve you're main problem, but that actually isn't part of the API. If you go to api.stackexchange.com you kind information on how to get the data "raw", in JSON format. Sadly however the API doesn't let you get reputation changes for multiple days at once, so you're still stuck with making lots of GET requests. (I'm curious how you ...


2

You need to pass your request key as well. I'm not sure what you're using that isn't giving you the error message back, but if you had captured it you would have seen it said something like: { "error_id":405, "error_name":"key_required"," error_message":"`key` is required when `access_token` is passed." }


2

As with suggested edits*, tag wikis, privileges, and so on... we don't expose things in the API until they've settled down quite a bit. Also, "Whole network" APIs are something that take a bit of work to get adequately performant. A lot of effort went into getting the network profile pages to scale properly, similar effort will be needed on the API for ...


2

This has been fixed. There was effectively a missing where clause on that route. Very odd.


2

JSON API Note: I am just one developer and I do not have the time/money/resources to maintain an industrial grade public data source. If it is determined for any reason that you are not using the API in the capacity and terms indicated, your IP will be banned with a quickness. I will shortly implement a private key system. Those interested in using the ...


2

Find Stack Exchange Users By UserName OR Email You may find any user in the Stackiverse by the email address they supply when registering on any Stack Exchange site or by full or partial user name (display_name). JSON API { "email_address": "foo@bar.com", // yes - this is a real account "items": [{ "site_url": ...


2

accept_rate is the internally tracked value of the user's Accept Rate. This is roughly a measure of how many of the user's questions have answers and where one of the answers was accepted by the user. For the actual details of how it's calculated, read the blog post announcing accept rate. In a nutshell: The user must have 4 or more questions. Only ...


2

That is not URL encoding, that is HTML entity encoding. By default, the API returns "safe" values; see the filters doc: Any string returned as a result of an API call with a safe filter will be inline-able into HTML without script-injection concerns. That is to say, no additional sanitizing (encoding, HTML tag stripping, etc.) will be necessary on ...


1

The API path you want is /users/{ids}/associatedDoc. It takes global, Stack Exchange account_ids and returns all the site-specific user_ids for the specified users. For example, your user_id for Stack Overflow is 2257664 and your global Stack Exchange, account_id is 2606599. (You can see your /associated results, here.) You can get user account_ids from ...


1

The creators' ideas for future improvement - if somebody actually uses the plugin, we'll possibly implement some of these: Possibility to configure a different color for every SE site (because one-color-for-all approach is working, but there's no single color that would fit all of them nicely). Possibility to configure a different color for any user. Make ...


1

Some changes to the site display of a user's timeline percolated up to the API interface. They've been decoupled, and things should be back to normal.


1

Drill-Down An evolving feature of the StackApps platform is drill down on any user. The utility and polish of the features are somewhat affected by the fact that I am cutting my teeth on the completely different, and refreshing, paradigm that MVC presents. So bear with me. And email me suggestions as to what you would like to see. Current features ...


1

Client-side Live Updates With 370,000 rows of user data to maintain, it is an impossible task to keep every record updated up to the minute. To mitigate relatively stale data on volatile fields such as last_access_date, StackUsers offers optional client-side updates of results using Soapi.JS2. You must opt in by either clicking the Enable Live Update ...


1

CSV output Any grid on StackUsers provides an Export CSV to Clipboard button that will copy the data from the current grid view. This includes all user fields, not limited to those shown in the grid. The output is standard CSV and can be opened or consumed by any tabular data editor. Anonymous StackUsers can page 50 rows, while registered users are ...


1

StackAnywhere has so far not attempted solve this problem. A similar issue exists for question lists. In fact it's more likely to be an issue here because when the list is sorted by date, new questions can push others down the list resulting in duplicate entries. It's an open issue in the StackAnywhere bug tracker at the moment.


1

I can't reproduce this bug, both queries return what I'd expect (and variations work as well).


1

You get it from the users route, like I told you in your last question. You can't use the Id from the stackexchange website. But in version 2.0 of the API you will highly likely be able to again.


1

As a sort of quick experiment, I slapped together a regex scraping of a single user's accounts page on SE.com and have put it up on the test deployment of se-flair: http://test.se-flair.appspot.com/SEaccounts/[assoc-id]/ The return is, at the moment, a JSON object with the display name, the gravatar URL, and an array of sites, where each site has the ...


1

association_id appears in the returns of /users/{ids} for user's who have existing associations. For example: ... more ... " up_vote_count": 871, "down_vote_count": 48, "accept_rate": 82, "association_id": "f403b833-81b1-421c-96e6-ede6e9efb3c4", "user_questions_url": "/users/80572/questions", "user_answers_url": "/users/80572/answers", ...


1

UPDATE: min/max on users by name is now case insensitive resulting in a viable 'exact match'. e.g. min=john&max=john see http://stackapps.com/questions/1060 the min/max solution that codeka presents seems to work great. While it does not guarantee accurate results, it does drastically reduce network traffic. I simply check again when I get the ...


1

This has been fixed.


1

Current API is read-only, and /users/recent info can only viewed by yourself (404 for other users). So, API shouldn't expose the informations that real site doesn't. Actually, there is users/timeline option in API, that could be work around, except for voting processes.



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