A summary of the main things you need to know to use the ipernity API. Each point is detailed in other available documentation.
To begin, let us agree on some terms:
Your API key uniquely identifies your application. This key will be requested every API call. Note that each key is accompanied by a secret. This code will allow you to sign your API requests and ensure their authenticity. The API keys are free but subject to the acceptance of the ipernity API Terms and Conditions of use. Would you like to get your key now?
It's up to you to decide. You might want to keep your application secret, or benefit from a wide audience. During development, please keep your key active but hidden. Statistics are available to monitor the activity of your application.
If you want to chat with users of your application, create a group and link it to your application.
The API is a web service that responds to the HTTP protocol on the url http://api.ipernity.com/api. Applications may be sent by GET or POST. Here we have the classic example of hello world.
http://api.ipernity.com/api/test.hello/xml?api_key=6fa87ba(..)fe457Items in the following url are:
test.hello : the name of the API method called. (test.hello)xml : the desired output format.api_key : the API key.<api status="ok"> <hello>hello world!</hello> </api>Requests to modify data must be sent by
POST action.
The secret guarantees the origin and authenticity of API requests. All sensitive methods such as altering data or access to private objects should be signed with the secret. This is not complicated. Take a look at the documentation about encoding and signatures, or be inspired by one development kit.
We advise you to automatically sign your requests. If you must, check calls to the API will always be signed in the settings of your key. This will prevent anyone from using your API key without your knowledge.
Imagine that your application can modify the tags of documents. A member wishing to use it has to give permission for your application.
Specifically, your application will redirect the member to page showing the required rights it wishes. The member must then approve the access requested. Access rights are granted until the member withdraws the application.
The API kits offer essential functions for using the API. If you can't find what you need you can easily write your own.
We created two groups for this subject: