0947fb9b69be138080febf2554d184667045d3a6 lrnassar Wed Oct 22 11:02:48 2025 -0700 Clarifying that API key generation is only available on primary website and not mirrors, refs #31058 diff --git src/hg/htdocs/FAQ/FAQdownloads.html src/hg/htdocs/FAQ/FAQdownloads.html index 460fd87aea4..054468a690e 100755 --- src/hg/htdocs/FAQ/FAQdownloads.html +++ src/hg/htdocs/FAQ/FAQdownloads.html @@ -1293,28 +1293,30 @@
The difference in the conservation scores, for both PhastCons and PhyloP, is that the wiggle database format (from which the details page and Table Browser scores are extracted) uses lossy compression that keeps enough resolution to display the pixelated scores in the browser graphic display but does not reconstruct the true original scores. This is why we make the original score files available for download.
To access the UCSC Genome Browser programmatically and bypass the CAPTCHA, all requests must include an API key. Note that an API key is not needed to use our REST API.
+API key access is only available on our primary site (not available on genome-euro or genome-asia). To generate your own key, first log in with your UCSC Genome Browser account. Once logged in, go to the Hub Development page and generate a key +target="_blank" href="https://genome.ucsc.edu/cgi-bin/hgHubConnect#hubDeveloper"> +Hub Development page and generate a key from the API key section at the bottom of the page.
The key must be appended to your request URLs using the apiKey= variable.
Separate it from other URL parameters with an ampersand (&). For example, most queries will
work by adding apiKey=YOUR_UNIQUE_KEY to the end of the URL:
https://genome.ucsc.edu/cgi-bin/hgTracks?db=hg38&apiKey=YOUR_UNIQUE_KEY
If you experience any issues using the API key, please contact us.