) just announced that APIs currently available to applications hosted in zembly is now available outside of zembly
, say from a Java desktop application, by the Zembly Client Library (ZCL). To secure the API call to protected resources, ZCL in conjunction with zembly uses the security mechanism specified by the OAuth protocol.
The client library hides all the plumbing in making the secure call. For the most part, the developer task is reduced to copying and pasting code snippets to her Java or JavaFX client code.
Zembly’s keychain page facilitates the generation of two kinds of keys that are required for calling services to protected resources. The first one, dubbed as the “Master key” is the OAuth consumer key and secret that is required in the client code. It is the key to enter the “zembly gateway” so to speak. With a simple click of the mouse, this key is generated and stored for you in zembly. The second, which we will call the “API key” is the key that you normally apply for when calling public APIs such as those from Amazon, Flickr, or Google. The keychain page likewise facilitates the generation and storing of this key.
As a side note, the zembly user experience has been enhanced with the addition of the Browse APIs page. In this page, the developer can navigate through the numerous public APIs that she may want to call either within zembly or outside of zembly. My favorite part of the page is the Test Drive button which, as the name implies, allows the developer to test or preview the API of her choice.