imageloop API
See imageloop API in action in our Showcase !
This page gives an overview of the imageloop API. All API calls do only use standard HTTP requests to our imageloop server via TCP port 80. This means, that your applications work, if your browser can access imageloop. Standards like HTTP, XML and SOAP guarantee fexibility and fit into existing network infrastructures.
Developers will find information and tools to build their own applications using imageloooop. imageloop offers its API and language kits for several programming languages like JavaScript, PHP, ActionScript, Java, C# or VB.NET.
An API key is required to use the imageloop API or a language kit. There are two different kinds of API keys:
- API keys for applications running on web pages inside a browser (JavaScript) and
- API keys for standalone applications (Java, PHP, C#, VB.NET, ActionScript)
Language Kits
Ready to use libraries for these programming languages are available from imageloop or a 3rd party.
Transports
imageloop API supports several transportation mechanisms. All transportation mechanisms support the same functionality and require HTTP session tracking using a cookie (see below).
Take a look at this page for more information about SOAP transport.
WSDL file can be downlaoded from http://www.imageloop.com/soap/api/api.wsdl, which referes to the XSD file http://www.imageloop.com/soap/api/api.xsd.
Take a look at this page for more information about XML schema objects.
HTTP session
Please note, that most functions (especially when a login is required) rely on working
HTTP session handling.
HTTP session handling in imageloop is implemented using a
session cookie named JSESSIONID. This value of this cookie is the ID of
the current HTTP session.
Usually all common SOAP client implementations support HTTP cookie tracking. The language kits for
Java and .NET use functionality provided by the frameworks. Our JavaScript language kit
"uses" the functionality provided by browsers.
You can test, whether your framework provides working HTTP cookie handling by calling
the API function imageloop.getSessionId twice. If the same value is returned
by both calls, HTTP cookies work. If two different values are returned, your framework
does not provide a working HTTP session tracking. In this case, you have to implement
your own session tracking.
To implement your own session tracking, you can do either:
- Wait for the HTTP header
Set-Cookieand pass the cookie value in all following requests to our application in the HTTPCookieheader. - Or you can query the session ID using the API method
imageloop.getSessionIdand pass this value in all following requests to our application in the HTTPCookieheader. - Note: the HTTP session ID changes when a user logs in or logs out!
english
deutsch
français
español
italiano
türkçe