Hot answers tagged

6

AFAIK StackExchange network uses gravatars. Hence you can get their profile picture from their email address (check the gravatar site for details).


6

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


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

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


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

You can use /users/{ids}/associated Try it for your network account Returns all of a user's associated accounts, given their account_ids in {ids}. {ids} can contain up to 100 semicolon delimited ids, to find ids programatically look for account_id on user objects. You can filter the network_users returned by this method with the types ...


4

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


4

The API does not provide any method to determine a user's email address and it is unlikely to do so in the future. This would be a risk to both the user's privacy and his/her trust in Stack Exchange. And, a pressing need for this information has yet to be demonstrated, regarding the API. Note that Stack Exchange refuses to even provide the user's email hash ...


4

Your stated problem is considerably easier than the question you linked. You can use the /users/{ids}/answers route to get what you want -- with a little work. The trick is to use a filter that returns the answers.tags property. In your case, if you really just want totals, and for one user at a time, you can use the filter: !GeF-5u(cSumXA . The ...


3

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


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

Why can't we get a separate site just for API testing? We just need another community site that is not used for other purposes. The scores are separate, so there is no penalty for posting junk to it. If there is enough interest, we can probably just create an vote for another site...... Maybe start describing and demonstrating specific use-cases for ...


3

Eventually, yes. Please see this answer for some more details. The short of it is, there isn't really a good place to shove this kind of data yet. Especially if you're planning for the Count(Sites) > 5 case, which we are. StackAuth implements this feature now.


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

Until the feature request is approved, you can get this number in one of 3 ways: You can get slightly stale data with this SEDE query. Note that it uses your Stack Exchange account number (4337810 for the OP) -- which you can get by clicking on the "Accounts" listing of any profile page. Or, You can make a boatload of API calls to get the current ...


3

Use the /users/{ids} route to get account_id. Then pass the account_id to /users/{ids}/associated. Note that account_id is exactly the kind of information that should be heavily cached by your script/app. (Hint, hint; wink, wink; nudge, nudge. (^_^) ) For example: /2.2/users/10349?site=superuser&filter=!T6o*9deY.2ZD3-(n4f Returns: { ...


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


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

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.


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

This should be fixed now. (Its kind of safe to assume these are bugs by the way, we are in beta)


2

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


2

Actually, the API does this already, and I'd prefer this method over using my email address. In fact, the reason for the Stack Exchange API is so that our apps don't have to rely on third parties that may break, change their APIs, misuse our data, or go away. Additionally, if your app doesn't need access to sending me emails, then I'd just prefer you not ...


2

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.


2

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


2

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.


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



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