8edff70d53e7dfe812ccb5c95a452fb2f4831716
hiram
  Fri Apr 19 10:22:32 2019 -0700
adding the jsonOutputArrays option refs #18869

diff --git src/hg/htdocs/goldenPath/help/api.html src/hg/htdocs/goldenPath/help/api.html
index 2efd0ef..239d3f1 100755
--- src/hg/htdocs/goldenPath/help/api.html
+++ src/hg/htdocs/goldenPath/help/api.html
@@ -82,54 +82,55 @@
 <!-- ========== Parameters to endpoint functions ======================= -->
 <a name="Parameters"></a>
 <h2>Parameters to endpoint functions</h2>
 <p>
 <ul>
 <li>hubUrl=&lt;url&gt; - specify track hub or assembly hub URL</li>
 <li>genome=&lt;name&gt; - specify genome assemby in track or assembly hub (only used with hubUrl)</li>
 <li>db=&lt;ucscDb&gt; - specify database (aka genome assembly) in UCSC genome browser (either hubUrl or db specified, not both)</li>
 <li>track=&lt;trackName&gt; - specify data track in hub or UCSC database genome assembly</li>
 <li>chrom=&lt;chrN&gt; - specify chromosome name for sequence or track data</li>
 <li>start=&lt;123&gt; - specify start coordinate (0 relative) for data from track or sequence retrieval (start and end required together)</li>
 <li>end=&lt;456&gt; - specify end coordinate (1 relative) for data from track or sequence retrieval (start and end required together)</li>
 <li>(see also: <a href='http://genome.ucsc.edu/blog/the-ucsc-genome-browser-coordinate-counting-systems/' target=_blank>UCSC browser coordinate counting systems)</a></li>
 <li>maxItemsOutput=1000 - limit number of items to output, default: 1,000, maximum limit: 1,000,000 (use <em>-1</em> to get maximum output)</li>
 <li>trackLeavesOnly=1 - on <em>/list/tracks</em> function, only show tracks, do not show composite container information</li>
+<li>jsonOutputArrays=1 - on <em>/getData/track</em> function, JSON format is array type for each item of data, instead of the default object type
 </ul>
 </p>
 <p>
 The parameters are added to the endpoint URL beginning with a
 question mark <b>?</b>, and multiple parameters are separated with
 the semi-colon <b>;</b>.  For example:
 <pre>
 https://api-test.gi.ucsc.edu/getData/sequence?db=ce11;chrom=chrM
 </pre>
 </p>
 
 <!-- ========== Required and optional parameters  ======================= -->
 <a name="Parameter use"></a>
 <h2>Required and optional parameters</h2>
 <p>
 <table border=1>
 <tr><th>Endpoint function</th><th>Required</th><th>Optional</th></tr>
 <tr><th>/list/publicHubs</th><td>(none)</td><td>(none)</td></tr>
 <tr><th>/list/ucscGenomes</th><td>(none)</td><td>(none)</td></tr>
 <tr><th>/list/hubGenomes</th><td>hubUrl</td><td>(none)</td></tr>
 <tr><th>/list/tracks</th><td>(hubUrl and genome) or db</td><td>trackLeavesOnly=1</td></tr>
 <tr><th>/list/chromosomes</th><td>((hubUrl and genome) or db) and track</td><td>(none)</td></tr>
 <tr><th>/getData/sequence</th><td>((hubUrl and genome) or db) and chrom</td><td>start and end</td></tr>
-<tr><th>/getData/track</th><td>((hubUrl and genome) or db) and track</td><td>chrom, (start and end), maxItemsOutput</td></tr>
+<tr><th>/getData/track</th><td>((hubUrl and genome) or db) and track</td><td>chrom, (start and end), maxItemsOutput, jsonOutputArrays</td></tr>
 </table>
 </p>
 <p>
 The <b>hubUrl</b> and <b>genome</b> parameters are required together to
 specify a unique genome in an assembly or track hub.  The <b>genome</b> for
 a track hub will usually be a UCSC database genome.  Assembly hubs will
 have their own unique <b>genome</b> sequences.
 </p>
 <p>
 When not an assembly or track hub, to access UCSC database assemblies,
 the parameter <b>db=&lt;name&gt;</b> is required.
 </p>
 <p>
 Using the <b>chrom=&lt;name&gt;</b> parameter will limit the request
 to the single specified chromosome.  To limit the request to a specific