For an initiative that aims to make it easy to share data and intellectual property, however, Creative Commons can appear, at first sight, to be very un-Web-2.0 [do not sue me O'Reilly]. A developer who happens to casually surf the CC website can easily leave thinking that the only way to integrate a CC license into her web application is to use an ugly HTML-based system that requires users to be redirected to the CC website. She may be left thinking, as I was: "Where is my open Creative Commons API?"
The good news is that it exists. The bad news is that information about it (and other APIs) is well hidden!
Here are three relevant links where you can learn about the Creative Commons REST API and other developer aids:
- Creative Commons Developer Aids and APIs
- Creative Commons Web Services (REST API)
- APIs for Creative Commons license metadata
And here are a few other links to important Creative Commons pages:
- Main Creative Commons page for developers.
- Using Creative Commons metadata.
- CC Tools: Tools to tag and verify Creative Commons-licensed works
The Creative Commons initiative is currently lacking two important things: The first is widespread support for embedding Creative Commons licenses in third-party applications and the second, and most important thing, is a solid search solution for Creative Commons content. There are several search solutions for CC content but none of them provide an easy means to narrow down a search by license. Hopefully, better visibility of the developer APIs will spur new developments in these areas.
The Opening up Creative Commons article by Aral Balkan, unless otherwise expressly stated, is licensed under a Creative Commons Attribution-Noncommercial 2.0 UK: England License.

Add Your Comment