Knowledge and experience of building API websites. I've been an employer on freelancer for over 2 years now and have worked with numerous developer. I understand everyone has to start from the bottom and learn their way up. However, I'm only looking for professional on this project. You must have the skills!
I will provide for you a complete psd website template with all the features and layout. Your job is to program the backend using the campusbooks API and widgets ( I'm attaching a complete campusbooks API Tutorials and Widget tutorials). The website needs to be SEO friendly and it need to be able to work on multiple websites using the same query database. I want to run this script on numerous websites.
Upon completion: You will provide to me a working website, that is SEO friendly, and can work on multiple website query the main database.
Note: Max Bid accept is $450.
Thank You :)
CampusBooks.com API Documentation (version 12)
The CampusBooks API allows permitted partner sites to utilize the power of the CampusBooks technology on their own websites and applications. The API is implemented via an HTTP GET request in a standard REST format. Results are returned in XML format.
This document specifies the protocol for submitting queries to the CampusBooks API and the results it will return
Version 4 of the API builds upon version 3 by including additional pricing detail for book rentals. These offers have a priced based on the number of days that the book is rented. The default price return in offer::price is for the semester price. Other rental periods are contained in the offer::rental_detail array
Version 5 adds a searchid parameter to the bookprices, buybackprices, and prices requests. This may aid in future functionality
Version 6 adds optional image_width and image_height parameters to the search, bookinfo, bookprices, and buybackprices requests. The book image returned by the API will be of the size specified in either of these parameters. If both parameters are given, only image_height will be used and image_width will be ignored. This version also includes merchant logos for each offer in the prices, bookprices, and buybackprices requests.
Version 7 just makes some internal changes
Version 8 made some additional internal changes
Version 9 adds the abilty to return a response in JSON format
Version 10 adds coupon and home page link features
Version 11 updates filter for coupon and changes home page link format
Version 12 provides faster overall response times and dramatically fewer request timeouts in both book and price comparison searches
If you're using API v11, switching to v12 is easy. Within your existing API requests, change the following in the URL:
Response data between v11 & v12 is formatted similarly so no modifications other than that listed above are necessary.
Note: Updating from older versions (v3 - v10) is "at your own risk." The formatted response data will be similar, but may not be exact. Please reference the remainder of the documentation to ensure proper usage.
If you encounter any issues, please let us know. New API v12 is completely backward compatible to v11 from a user perspective and with all the benefits of behind-the-scenes optimization.
Each request to the CampusBooks API may contain the following parameters:
Call The Name of the function that you want to call
Key This is the API Key assigned to you. It is unique to your site and is required for all calls
The API has a default timeout. When the timeout occurs we take all available results collect and return them to you. The default timeout is variable and managed by our system to maximize results. In most instance we set it between 5.5 and 6 seconds.
Should you choose to want results faster, or to ensure you get more results you can set your own timeout. To do so add "&timeout=X". X can be as low as 3 and as high as 9.
Remember that by setting your own timeout you may effect your results. If you want to test consider using different ISBN's as we cache data so initial results may vary if you hit the API for the same ISBN several times in a row.
Additional Arguments Some calls accept (or require) additional parameters that can be passed as additional parameters in the GET request
The root element of the XML returned will be a <response> element. The 'status' attibute indicates either 'ok' or 'error'.
On success, the <response> will include a <page> element with the results of your request. On failure, the <response> element will contain an <errors> element containin a list of any errors that occurred