Is there a way to retrieve the number of notes on a tumblr post, without an API key?
You can use the free API key in the documentation. I guess you dont want to register or you want use the Javascript API, which exposes you API key to the public:
https://www.tumblr.com/docs/en/api/v2#posts
Related
I need to get the coordinates from the browser and get the address of those coordinates. For that I can use the Bing Maps Location api (https://dev.virtualearth.net/REST/v1/Locations/*long*,*lat*?c=fi&o=json&key=*myapikey*).
How secret should I keep this key?
When embedding Bing Maps you also need a key that would be seen in the browser. Not sure how that key compares to the Locations api.
Should I create a separate key for those calls?
Can I do the api calls from javascript which would expose the key?
The alternative being that the frontend does a backend call with the coordinates and the backend is calling the Maps api.
Generally speaking you should keep your key private as anyone who gets the key can make transactions which would be billed to you. In practice this has not been a huge issue and it's easy to block a key and get a new one if this occurs. If you want to be more secure, keeping the key server-side and routing your client calls through the server will protect it. You can also generate a session key from your API key on the server when the page is first rendered and send that to the client. A session key works like a normal key, but has a short expiration time, so there's no danger of it leaking and being used by someone else.
I would like to use the GitHub API to get a log of all API requests made using a specific API key. I couldn't find anything in the GitHub API documentation about getting a history of usage for my API key. Is this possible?
All,
Getting "REQUEST DENIED" when I try to access Google Maps Geocoding web service. Not sure why. The URL looks right to me and the Simple Access API browser key is valid and has both Maps v2 and Maps v3 turned on.
I realize the API key is no longer required in v3 so I have no idea how to get around the API limits using the web services via query string params.
http://maps.googleapis.com/maps/api/geocode/json?key=MYAPIKEY&latlng=39.76144296429947,-104.8011589050293&sensor=true
When I remove the "key" parameter, it works but I need stats and don't wanna hit the API access limits so I need the key in there (I think)
Any suggestions would be great.
Thanks
Decided to go with geonames.org for this project. Much easier to deal with than Google.
I was wondering if there is a way to create new fields in a profile? For example, could I write an add-in of some sort that put a PGP or S/MIME encryption key in my profile and make it part of the public profile?
I walked through the API documentation and these forums and I didn't see a way to make this happen.
Basically the end-game I want is to use FQL to search for these keys.
There doesn't seem to be a place to stash this sort of generic meta data per user using the Graph API. And that makes sense, when you think about it. Otherwise all kinds of junk could be stored there...
So you would probably need to keep this data on your servers or through an App that the users authorize (and then you could theoretically add it to the graph as some connection, like "userX 'encrypts with' this_public_key")..
I've never used an API and was wondering how you use them... I would like to use facebook, twitter and vimeo's api,
Can someone explain the basics of using them, how do i access them and use them etc.
Please and thanks
Neil
How to use an API depends on the API. Usually the API creator has documentation on how to use their specific API.
Mostly, things work like the following:
You register to get a developer key. Then, you send requests to the service via HTTP (for example Twitter is using REST, which requires you to send XML or JSON to a specific http-URL providing your key). You get an answer from the service, which you must then parse and react to accordingly (for example filling a list with contacts, etc.).
Most of the time this all comes down to:
Create an XML or JSON document that describes the call parameters
Send the document to an URL using GET, POST or other request methods
Get the server's response
Parse and evaluate the response
The specific ways to use the API, especially performing authentication, can be found on the service's developer pages.
The best way to start if you want to use an API is to read it's documentation, find some tutorials and code examples. This is always/usually published by the one offering an API.
Good luck :)