ePHOTOzine Developer API
Join ePHOTOzine for free and remove these adverts.

If we were to create a public API, it would probably initially be read-only. No doubt we would put some usage monitoring to ensure no one is using it to heavy. Eventually we could then create write access calls too.
There will probably be restrictions in place when it comes to user data and photos.
It's just an initial query to see what sort of interest is out there (if any) from developers. Would it be something you would want to work with?
There will probably be restrictions in place when it comes to user data and photos.
It's just an initial query to see what sort of interest is out there (if any) from developers. Would it be something you would want to work with?

Quote:I'm still curious what you think the need is for this ?
That's partially the reason for the topic. To see if there is any interest/need for this. I'm sure you would agree that public APIs have done wonders for many other websites, but there must be an interest and desire from some developers before doing so.
Lets say the restrictions/licences are as open as flickr's api (as an example). Feel free to comment on what YOU think the restrictions/licences should be.

lol, I think as an initial thought, a public API would be provided to encourage development, not as a way to con developers into paying us money. If anything, maybe we could find a way to pay developers for there contribution to revenue generated via apps they create. Again, just talkin, nothing is in stone here.