You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Bravo variant browser currently shows chromosome locations, alleles, VEP functional annotations, and allele frequencies for 463 million variants observed in 62,784 individuals sequenced in NHLBI's TOPMed program. https://bravo.sph.umich.edu/freeze5/hg38/about
There doesn't appear to be a swagger JSON, but it's a fairly standard REST-like RPC API, so an OpenAPI description should be straightforward.
Open question: this API (and the browser) requires authorization and authentication (using google for authentication). The setup has clear instructions on how to do this. I assume we want to indicate this in the API registration metadata; how best to do this? Do we want KC6 input on this?
The text was updated successfully, but these errors were encountered:
The Bravo variant browser currently shows chromosome locations, alleles, VEP functional annotations, and allele frequencies for 463 million variants observed in 62,784 individuals sequenced in NHLBI's TOPMed program.
https://bravo.sph.umich.edu/freeze5/hg38/about
There is an API here:
https://bravo.sph.umich.edu/freeze5/hg38/help
There doesn't appear to be a swagger JSON, but it's a fairly standard REST-like RPC API, so an OpenAPI description should be straightforward.
Open question: this API (and the browser) requires authorization and authentication (using google for authentication). The setup has clear instructions on how to do this. I assume we want to indicate this in the API registration metadata; how best to do this? Do we want KC6 input on this?
The text was updated successfully, but these errors were encountered: