Using Paged Results


Search for all round pills, using a page size of 2 images, requesting page 3.


Performing many queries such as the example given here of round pills will generate a large number of results, far more than a client application would normally want to display to the user on a single screen. To facilitate optimal server response and data transmission times it is therefore recommended to use paged results. In this example we set a page size of two images, which results in 409 pages, of which we request page 3 (response numbers based on queries made on 15-April-2013). A client application will always request page 1 initially, then read the total number of available pages from the replyStatus.totalPageCount element. Subsequent API requests are then made to request each page in turn as they are required. Requesting a page that does exist will result in an error return.

Reply, JSON format

         "name":"Terbutaline Sulfate 5 MG Oral Tablet",
         "labeler":"Lannett Company, Inc.",
         "name":"Cyclobenzaprine hydrochloride 10 MG Oral Tablet",
         "labeler":"Pliva Inc.",

Reply, XML format

<rxImageAccess xmlns:xsi="" xsi:noNamespaceSchemaLocation="">
      <name>Terbutaline Sulfate 5 MG Oral Tablet</name>
      <labeler>Lannett Company, Inc.</labeler>
      <name>Cyclobenzaprine hydrochloride 10 MG Oral Tablet</name>
      <labeler>Pliva Inc.</labeler>

Response Referenced Images

00527-1311-01_rxnavimage10_2d2696b4.jpg 50111-0563-01_rxnavimage10_6b243581.jpg

Page Tools