Welcome to Feedbooks.com !
|
Application Programming Interface (API)
E-mail Us
Feedbooks is open to third party developpers via an Application Programming Interface (API), based on the principle of a Representational State Transfer (REST) architecture.
In its current version, the API is read mostly, but with new endpoints using the POST/UPDATE/DELETE requests this will change in the future.
Feedbooks old API is still accessible here but won't be updated anymore.
Feedbooks old API is still accessible here but won't be updated anymore.
RESTful Resources
Our API and our website share similar resources, and most of the time you'll just have to change the file extension to use the API instead of the website. For example, if you'd like to search for a book with the query "Paper":
We use this design pattern everywhere on the website, for example for a book you'll have:
We use this design pattern everywhere on the website, for example for a book you'll have:
- XHTML: /book/id
- ePub: /book/id.epub
- PDF: /book/id.pdf
- Mobipocket: /book/id.mobi
- Cover: /book/id.png
Encoding
All requests and answers on Feedbooks are in UTF-8. If you're using parameters, remember to correctly encode your URI.
Authentication
Some endpoints on Feedbooks require to be authentified, while some other might provide additional features if you're authentified (for example, sending your credentials while requesting a download will log your download).
There's 2 different ways to get authentified:
There's 2 different ways to get authentified:
- Parameters: http://url?user=username&password=MD5Hash
- HTTP Basic Auth: curl -u username:MD5Hash http://url
Endpoints
We've grouped together endpoints that share similar patterns:
Once you've implemented an endpoint in one of these groups, it's usually fairly easy to implement the rest of them.
Once you've implemented an endpoint in one of these groups, it's usually fairly easy to implement the rest of them.
