Hot answers tagged api-key
2
It depends on what profile information you need to display.
Basically anything in a user's profile that's public-facing is exposed via the API and requires no action on behalf of the end-user. Starting with v2.0 of the API, you have limited access to some private user information (such as the their full reputation history) through the OAuth 2.0 methods.
In ...
2
key is your app key, access_token identifies a user (and a set of permissions) and is what you get at the end of an authentication flow.
Keys are not secret, for example here's what the Documentation Console's registration looks like:
You can find your app key by going to Manage Your Applications (in the Stack Apps homepage sidebar) and selecting one of ...
1
For one use the current API version (2.1) instead of an old one (1.1 in your case).
Furthermore, when using JSONP you do not have to parse the result. The data object you get in your success method already is a JavaScript object you can work with.
$(function(){
$.ajax({
url: ...
1
The API expects JSONP requests to specify the callback as the jsonp parameter, not the callback that jQuery uses by default.
While really you should consider upgrading to API 2.1, which does expect callback (and allows CORS, for that matter), you can fix your code by putting in the jsonp parameter placeholder:
$.ajax({
...
1
"When I requested the Key I provided application site. What is purpose of this site ? Can it be just my home page, git account or a personal blog ? Or do I need to implement some functionality on this site ?"
As far as I know, the application site field exists purely for documentational purposes. You can provide the name of your blog or a GitHub page if ...
Only top voted, non community-wiki answers of a minimum length are eligible
