| Home Beta programs |
Welcome to Mobipocket Developer Center |

eBookBase Retailer IntegrationGetting StartedOverviewSteps to IntegrateWhat's new in V3Mobi Reader Desktop eBookstoreFAQ eBookbase V3 Create a Purchase TransactionDownload of free sample ebookUser LogonUser Online LibraryUser Device ManagementTesting Samples for eBookbase V3 Generate the Hashcode parameter for NewTransaction (ASP)Generate the Hashcode parameter for NewTransaction (JSP) |
Mobi Reader Desktop eBookstore IntegrationStarting with the release of Mobi Reader 5.0, the PC based Mobi Reader Desktop client includes a built-in functionality which enables users to browse an eBookstore, purchase and download items directly from within the software. To be listed as an eBookstore in Mobi Reader Desktop, an eBookbase Retailer must follow these steps:
Implement a user logon validation web service To authenticate a user when activation or reactivation of an ebook file is required, Mobi Reader Desktop requires the user to logon to the retail site where the ebooks were purchased. Mobi Reader Desktop gets the Username and Password from the user and sends these parameters to eBookbase. eBookbase in turn calls a user logon validation web service URL provided by the retail site, with the Username and Password as an input parameter. The URL returns the UserID corresponding to the user account in the retailer's system. This UserID must be the same identifier as the RetailerUserID parameter passed in the NewTransaction web service Syntax of the logon validation URL: http://myvalidationURL?Username=MyUser&Password=MyPassword The ValidationURL must accept two parameters in GET mode: Username and Password Output of web service: Important: the response of the web service must have the text/xml MIME Type. Example in ASP: Response.ContentType = "text/xml" Successful logon: <User><Id>My UserID</Id></User> Error cases: <Error><Code>my error code</Code><Description>my error desc</Description></Error> "Forgot password" link in Online Account Logon dialog box If the user has forgotten the password of his account, he can click on the Forgot password link in the Reader Desktop logon dialog box to retrieve the password by email. This links to a custom URL on your site that you must specify by including the following META tag in the html header of the home page of your Reader Desktop eBookstore: <html> Further optional integration of your eBookstore with Reader desktop functionalities
In the picture above which represents the Reader Desktop navigation bar, the link and label for "Science Fiction" is customizable. To make a custom link appear on any one of the web pages of your ebookstore, you must include the following META tag in the html header of the page: <html> N.B. : The URL is a link to the page on your site that is displayed when the user clicks on the item in the navigation bar; the blue arrow icon is currently not customizable
You can include a link on the detail page of an ebook for the user to download a free sample. The free sample download is a service provided by eBookbase. In order for the sample ebook download to integrate with Reader Desktop, i.e. display of progression of the download, and when download is complete, sample ebook opens directly in Reader Desktop, you must use the custom javascript command window.external.download. Example: N.B. : BookID is the ID of the eBook as provided in the eBookbase meta-data
available in the Retailer's account
When the user types a string in the Search box of the Reader, the search results page that is called is a custom web page defined on your retail site. To specify the URL of the search page, include the following META tag in the html header of the home page of your eBookstore: <html><
br><head><br><METANAME="mbp:search" URL="mysearchURL"> mysearchURL is the URL of a web page which accepts two parameters in GET
mode: N.B.: If no <META NAME="mbp:search"> tag is found on the start page, the Search box is greyed out or hidden by the Reader. The output of the search results is an XML structure conforming to a Mobipocket-defined format. The Reader will display the results using the integrated list view, as in the picture below.
The required XML output is defined as follows: <Root> |