Search Results

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 …

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 Returns all the users on Stack Overflow that have stack (case insensitive) in their display name. …

You could brute-force smaller sites that have less than 1 million users, but I wouldn't recommend it. You can search by location using SEDE. … For example:           Stack Overflow users who claim to reside in Bangladesh Note that SEDE data may be up to 1 week old and there is no API for it. …

If you want the reputation for a user, you would typically use the /users/{ids} route. EG:           /2.2/users/2765346? … EG:           /2.2/users/2765346?site=stackoverflow&filter=!40D.p(1f74CtdIRr7 …

That /users route works perfectly fine for showing the top users (of all time). For example to get the top 20 Mathematics users, use:           /2.2/users? … pagesize=20&order=desc&sort=reputation&site=math Which gives the same results as the top users page on math.stackexchange.com. …

The doc page says that the user object returns an age property (for those users that specified an age). But the API  no  longer  does.   … (Plus spot checks of users that had age in their profiles at one time.) Note that: Age was removed from users' (site) profile pages in April 2015. …

Get it via a call to the /users/{ids} route. For example:     /2.2/users/50274?site=stackapps Which currently shows your last_access_date as 1528358274. …

For example, here is a query to get your "About me" on stackapps: users-by-ids#ids=8109&filter=!. …

Those are the same numbers currently reported for you by /users/{ids}/associated. …

Use the /users/{ids} route to get account_id. Then pass the account_id to /users/{ids}/associated. … (Hint, hint; wink, wink; nudge, nudge. (^_^) ) For example: /2.2/users/10349?site=superuser&filter=! …

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

. <== Or, request that a /users/{ids}/edits route be added. …

So if you fetch: /2.2/users/1144996;6913068;6453670;1751488;73042;1840350/associated?page=1&pagesize=100 and /2.2/users/1144996;6913068;6453670;1751488;73042;1840350/associated? …

Anyway, the timeline does show all your events as can be seen with this query:     /2.2/users/4751173/timeline?fromdate=1563667200&site=stackoverflow where 1563667200 is midnight on July 21st, 2019. …

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. … (For most users, their non-numerical flair data is unchanged for years at a time.) …