{"id":19,"date":"2008-09-03T16:33:16","date_gmt":"2008-09-03T14:33:16","guid":{"rendered":"http:\/\/vladimir-shapiro.com\/en\/blog\/2008\/09\/03\/microstock-api-overview\/"},"modified":"2026-02-08T17:13:54","modified_gmt":"2026-02-08T15:13:54","slug":"microstock-api-overview","status":"publish","type":"post","link":"https:\/\/vladimir-shapiro.com\/en\/blog\/2008\/09\/03\/microstock-api-overview\/","title":{"rendered":"Microstock API Overview"},"content":{"rendered":"<p>Imagine you are a <a href=\"http:\/\/en.wikipedia.org\/wiki\/Microstock_photography\" title=\"What is microstock photography?\">micro stock photograph<\/a>. Also imagine your are not working exclusively for one agency but contributing to the top 5: <a href=\"http:\/\/www.istockphoto.com\/index.php?refnum=sonya_m\">iStockphoto<\/a>, <a href=\"http:\/\/submit.shutterstock.com\/?ref=93224\">Shutterstock<\/a>, <a href=\"http:\/\/www.dreamstime.com\/res274925\">Dreamstime<\/a>, <a href=\"http:\/\/de.fotolia.com\/p\/155566\/partner\/155566\">Fotolia <\/a>and let&#8217;s say&#8230; <a href=\"http:\/\/www.stockxpert.com\/\">Stockexpert<\/a>.<\/p>\n<p>Here is where the problem begins: each agency has its own rules, interfaces, submitting channels (HTTP, FTP etc.). Obviously, as the microstock marked is growing, there is a <a href=\"http:\/\/www.microstockdiaries.com\/what-microstock-contributors-want.html\" title=\"Lee Torents: what microstock contributors want\">need for additional services<\/a> and software both for and contributors and buyers.<\/p>\n<p>I also have a couple nice ideas in this area, so\u00c2\u00a0 I&#8217;ve done a short research on existing microstock API (Application Programming Interface).<\/p>\n<p><!--more--><\/p>\n<p><strong>Istockphoto<\/strong><\/p>\n<p>Istockphoto is the leading microstock agency and is known for its  uncommon upload process. The agency offers an <a href=\"http:\/\/www.istockphoto.com\/forum_messages.php?threadid=46006&amp;page=1&amp;refnum=sonya_m#\" title=\"API documentation and discussion on Istockphoto forums\">API based on XML-RPC protocol<\/a>, which includes download, upload, search and statistics functionality. Requesting API Key is not simple and it sounds like you need to apply for it with a serious business plan.<\/p>\n<p><strong>Shutterstock<\/strong><\/p>\n<p>According to <a href=\"http:\/\/submit.shutterstock.com\/forum\/post-309459.html\" title=\"API discussion on shutterstock forums\">the discussion on Shutterstock forums<\/a>, there is no API on horizon right now. As a result, some desperate members are developing statistics plugins like <a href=\"http:\/\/www.stockphotoideas.com\/shutterstockbar\/\" title=\"Official Shutterstockbar plugin page\">Shutterstockbar for Firefox<\/a>, which simply parses the HTML code of your Shutterstock profile. Of course, such findings are welcomed by community but not supported by Shutterstock administration.<\/p>\n<p><strong>Dreamstime<\/strong><\/p>\n<p>At first view the only thing the Dreamstime offers is its <a href=\"http:\/\/www.dreamstime.com\/referral.php\" title=\"Dreamstime referral program for contributors\">referral program<\/a>. At the end of the referral page, however, you can find a vague description of an &#8220;API\/XML feeds&#8221; available for registered users only. I&#8217;ve failed to find any detailed open documentation on the functionality but I believe you can get some Dreamstime content or even search on it using <a href=\"http:\/\/en.wikipedia.org\/wiki\/Web_feed\" title=\"Article about Web Feeds on wikipedia\">feed technologies<\/a> like RSS or Atom.\u00c2\u00a0 On the other hand, we also have here a <a href=\"http:\/\/www.dreamstime.com\/thread_6622\" title=\"Firefox plugin for Dreamstime: foum discussion\">discussion of a suitable Firefox plugin<\/a>, not welcomed by administration (as usual).<\/p>\n<p><strong>Fotolia<\/strong><\/p>\n<p>This agency leaves a solid impression: first search brought me to the <a href=\"http:\/\/groups.google.com\/group\/FotoliaAPI\" title=\"FotoliaAPI Google Group\">correspondent google group<\/a> with links to official <a href=\"http:\/\/www.fotolia.com\/Services\/API\/Introduction\" title=\"Introduction to FotoliaAPI\">introduction<\/a>, <a href=\"http:\/\/www.fotolia.com\/\/Services\/API\/Documentation\" title=\"Documentation for Fotolia API\">documentation<\/a> and <a href=\"http:\/\/www.fotolia.com\/Services\/API\/TermsOfUse\" title=\"Folotlia API: Terms of Use\">terms of use<\/a> for Fotolia API. The API itself is based on XML-RPC protocol and divided on several logical parts, depending on business case: Partner API, Business API, Developer API and Reseller API. Compared to competors, everything looks very professional and has a great potential for further development of the Fotolia community.<\/p>\n<p><strong>Stockxpert<\/strong><\/p>\n<p>According to the <a href=\"http:\/\/www.stockxpert.com\/info.phtml?f=help&amp;s=9_1\">official information<\/a> &#8220;API provides functionality to upload, search, display, purchase, and download Stockxpert images straight from the partner&#8217;s site&#8221;.\u00c2\u00a0 It is implemented via simple HTTP GET\/POST requests transferring serialized data using <a href=\"http:\/\/www.json.org\/\" title=\"Official JSON documentation\">Javascript Object Notation<\/a> (JSON) or in XML. Due to the simplicity of implementation this API\u00c2\u00a0 has its own limits (e.g. it is not clear for me whether it is possible to use it outside HTML forms). Anyway it is <a href=\"http:\/\/www.stockxpert.com\/info.phtml?f=help&amp;s=9_2\" title=\"Stockxpert API documentation\">partially documented<\/a> (better than nothing) and the <a href=\"http:\/\/www.stockxpert.com\/info.phtml?f=help&amp;s=9_3\" title=\"Stockxpert API example: photo search\">examples<\/a> show us that even with the limited functionality you can achive very nice results.<\/p>\n<p><strong>Summary<\/strong><\/p>\n<p>In general, the existing APIs (except of Fotolia) leaving an immature impression. A cold or sometimes even negative attitude to the problem by leading agencies\u00c2\u00a0 is also a bit discouraging. In the next posts I&#8217;ll try to figure out what are the major reasons for that. And of course I am going to drill down into the most perspective APIs in my sandbox to gain more practical experience on the subject.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Imagine you are a micro stock photograph. Also imagine your are not working exclusively for one agency but contributing to the top 5: iStockphoto, Shutterstock, Dreamstime, Fotolia and let&#8217;s say&#8230; Stockexpert. Here is where the problem begins: each agency has its own rules, interfaces, submitting channels (HTTP, FTP etc.). Obviously, as the microstock marked is [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[12],"tags":[],"_links":{"self":[{"href":"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-json\/wp\/v2\/posts\/19"}],"collection":[{"href":"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-json\/wp\/v2\/comments?post=19"}],"version-history":[{"count":1,"href":"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-json\/wp\/v2\/posts\/19\/revisions"}],"predecessor-version":[{"id":138,"href":"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-json\/wp\/v2\/posts\/19\/revisions\/138"}],"wp:attachment":[{"href":"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-json\/wp\/v2\/media?parent=19"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-json\/wp\/v2\/categories?post=19"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/vladimir-shapiro.com\/en\/blog\/wp-json\/wp\/v2\/tags?post=19"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}