See imagelooop API in action in our Showcase !
This page gives an overview of the imagelooop API. All API calls do only use standard HTTP requests to our imagelooop server via TCP port 80. This means, that your applications work, if your browser can access imagelooop. Standards like HTTP, XML and SOAP guarantee fexibility and fit into existing network infrastructures.
An API key is required to use the imagelooop API or a language kit. There are two different kinds of API keys:
Ready to use libraries for these programming languages are available from imagelooop or a 3rd party.
Java (Javadoc) Java language support library using the SOAP transport for integration into your Java applications.
PHP (Documentation) PHP language support library using both HTTP-RPC and SOAP transport for integration into your PHP applications.
.NET / SOAP Microsoft .NET support library using the SOAP transport for integration into your .NET applications written in Managed C++, C#, Visual Basic .NET or J#.
ActionScript (Macromedia Flash) / HTTP-RPC ActionScript language support library using the HTTP-RPC transport for integration into your web pages.
imagelooop API supports several transportation mechanisms. All transportation mechanisms support the same functionality and require HTTP session tracking using a cookie (see below).
SOAP RPC style SOAP transport function calls.
Take a look at this page for more information about SOAP transport.
WSDL file can be downlaoded from http://www.imagelooop.de/soap/api/api.wsdl, which referes to the XSD file http://www.imagelooop.de/soap/api/api.xsd.
HTTP-RPC URL encoded function calls with XML responses used in applications. The browser session is either tracked by a HTTP session cookie or the application sends the session ID as a URL suffix.
Take a look at this page for more information about XML schema objects.
HTTP-Client URL encoded function calls with XML responses used in interactive web pages. Requires the browser to support HTTP session cookies. A URL parameter specifies the XML stylesheet returns used by the browser to render the XML to valid HTML usable by human being.
Please note, that most functions (especially when a login is required) rely on working
HTTP session handling.
List of all API functions
image meta data
import and export
looop creation & deletion
looop meta data