202 votesLakin commented
This would be very useful. At the moment I keep most of the extra details in Notes which requires quite a few steps and means all of the information is visible. (For example, For a bank account I would have username/pass as the online banking details. In Notes would be the memorable details, security number or other such details they use for login. I also put in other information like account numbers, expire dates and plain notes). So when accessing just one bit of info a lot more is also visible.
It would even work if they were not true custom fields, but a bunch of optional standard fields like "Password2", "Card Number", "Memorable Answer", "PIN", etc.
Help us plan this. Please let us know what types of applications you have in mind. Or perhaps what systems you’d like to integrate with via the API.Lakin commented
I would like to add that having a public API would allow third party developers to create some of the other "top 10" suggestions:
Browser Plugin, Native iPhone/Android, Native Blackberry, Native Windows Mobile
My Personal plans for such an API are to develop a native desktop client. Probably just read-only to simplify syncing it would just be quicker to access than the webpage and allow - for example - me to access wireless keys stored while offline. It would also provide an automatic backup if your site is down, goes bust, etc.