Building an API

[john w]

I am feeling some pressure to build an api for the appraisal application. I use the WebApi for passing commands via html query strings. However, I need to move data using the api.

All of my data, to the degree it exists, lives in IMDB objects and text fields. I am not sure how to design it so the data can be passed to a third party.

I suppose I can use xml or json but is there a better way? Given the way the system works it appears the user would be pushing data rather than pulling it.

Do I build the api to my definition? I see trying to accomodate a host of 3rd party apps as a maintenance nightmare.

I am looking for suggestions about design, json vs xml, etc. Does InDe have any features that will make the creation of an api easier?

[ljwilson]

I'm not following if users are pulling data from your system, or pushing data (inserting records e.g.) to your system, or both.

Concerns are if it is publicly accessible, or if they need a login or unique token or whatever to control access.

The biggest thing is proper documentation so they know what to send and what they will receive.

...jack