Tag Info

Hot answers tagged

4

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

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


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


1

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


1

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


1

You can't as of now. It doesn't exist in the API. Here's a feature request I made - please upvote that for higher chances of getting this added! :)


1

You need to use a filter that returns those properties. The default filter does not. Also, the API is at version 2.2. You should use that unless you've a very good reason not to. So try, for example: http://api.stackexchange.com/2.2/users/55075?site=stackoverflow&filter=!G*ky*lRuarbDJTpnwEtY-a05oz Or: ...


1

No. You cannot search for a user by email address. Email accounts are sensitive private information and not disclosed by Stack Exchange. You can search for users by display-name though. See the documentation for /users. You can use the inname parameter. For example: /2.2/users?order=desc&sort=reputation&inname=Stack&site=stackoverflow ...



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