gtex-database

To interpret GWAS variants using GTEx eQTLs, you query the GTEx Portal API with a specific variant ID to retrieve tissue-specific regulatory associations, effect sizes, and p-values. This maps non-coding variants to their regulated genes.

Finding tissue-specific gene expression requires querying the GTEx API with a gene identifier to retrieve median TPM levels across various tissues. This identifies where your gene is most actively expressed within the gtex_v10 dataset.

Yes, you can use GTEx sQTLs to identify variants affecting splicing. Query the API by variant or gene to retrieve splicing quantitative trait loci, supporting mechanism-focused interpretation for specific tissueSiteDetailId datasets.

GTEx variant IDs require the format chr{chrom}_{pos}_{ref}_{alt}_b38. Using this exact identifier structure ensures successful JSON retrieval from GTEx REST API v2 endpoints when mapping variants to genes.

Yes, retrieving large result sets from the GTEx API requires handling pagination. When discovering eGenes active in a chosen tissue for multi-tissue prioritization, the query workflow manages pagination to return complete JSON responses.

The best way to prioritize genes for colocalization is listing eGenes active in a chosen tissue via the GTEx API. This retrieves tissue-specific regulatory data, supporting multi-tissue prioritization workflows for your downstream analysis.