This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
4thefile_api [2010/11/05 18:40] – jay | 4thefile_api [2010/11/08 21:53] (current) – jay | ||
---|---|---|---|
Line 2: | Line 2: | ||
The 4theFile API provides RESTful web services for use in integrating 4theFile with other web-based applications. The API has the following features: | The 4theFile API provides RESTful web services for use in integrating 4theFile with other web-based applications. The API has the following features: | ||
+ | |||
* all communication via HTTP or HTTPS | * all communication via HTTP or HTTPS | ||
* authentication via HTTP Basic auth | * authentication via HTTP Basic auth | ||
Line 62: | Line 63: | ||
If your web application' | If your web application' | ||
- | # your browser won' | + | - your browser |
- | # you would need to provide access to your API credentials in the client-side javascript, thereby exposing them in the client-side source code | + | |
- | so you'll need to provide your own ajax callback that in turn calls the 4theFile API (or provide a web proxy in the same origin as your server as described here http:// | + | So, you'll need to provide your own ajax callback that in turn calls the 4theFile API from the server, |
+ | Note: If you've read this far, you may be familiar with JSONP (an alternate solution to cross-domain ajax problems). We'd probably be willing to support JSONP as an alternative response format in the future if there' | ||