Howdy.  Is there a developer api for this?

Hello Sri. Developer API will be released this summer. 

One will be able to build a widget, software or anything with a smooth access to the data through Steek features (upload, browsing, sharing, streaming and so on...)

thanks for the Jeff.  Is there any documentation on how these widgets can be built (or is this once the API is provided?)

Cheers 

Documentation will be released just a bit before the API itself (I'd say a few days before). We would not want to release any documentation too early as the API content can still be modified even in the last days before going gold.

We look forward to what you guys will be able to do with it. Could you tell us a few words about it ? 

A widget for Netvibes (like the Box.net's one).

Jeff I understand...  but it would still be good to see some rough api out there and would be better (for steek) to get some feed back on how it could be made better...   just a suggestion... 

I agree with you Sri. We will do our best to find the right moment where giving you a documentation draft will benefit both to Steek and to the developer community. I will soon get back to this forum with a more specific timeline. 

sure no hurry at all:D 

Hi guys.

So you want to be a steekman... But what kind of API are you expecting? soa? xmlrpc? json? php extension? java/c/perl/python libs?

html and preferrably webdev would be great...

i would even say "rest" but i dont know much about it so itd just be tech-term-dropping on my part

I would think that webdav would be good as well, but that's just like ftp or http - it's not really an api.

As for xmlrpc, didn't that die a few years ago ? It's a bit tough to use as well, and SOAP its close cousin isn't that fun to use either

The most important thing for me would that all the data could be in xml format. If the data retrieved can be parsed with an xslt processor then integration into existing systems will be much more fun 

ah yes but REST isnt really an API is it? its simply a way of doing things (writing web apps in specific)...  please enlighten me if i have missed the point...   but having said that xml and json formats would be the easiest to parse (the latter being less verbose as well perhaps)...