[ensembl-dev] Ensembl REST API | GET eqtl/tissue/:species/

[Ramiro Magno]

Hi Thomas,

Thank you for your quick response. Let's wait for that new service then!

All the best,
Ramiro



On Wed, 11 Sep 2019 at 17:05, Thomas Juettemann <juettemann at ebi.ac.uk>
wrote:

> Hello Ramiro,
>
> Thanks for your message. I agree with your points. The eQTL adaptor was
> the first endpoint that I created, certainly room for improvement. ;-)
>
> eQTLs are moving to a different team, and a new dedicated eQTL server is
> work in progress, The beta server  should be available in latest a month at
> this URL:
> https://www.ebi.ac.uk/eqtl
> It is currently returning 404, but will be active soon. There will be a
> new API for you to play with if you are interested.
>
> For that reason we will not expand these endpoints further, I hope that
> makes sense.
>
> Thank you for going through them in such detail, that is much appreciated.
> Please let me know if you have any further questions.
>
> All the best,
> Thomas
>
>
> On 11 Sep 2019, at 12:00, Ramiro Magno <ramiro.magno at gmail.com> wrote:
>
> Hi Devs,
>
> I have a few questions about the endpoint "eqtl/tissue/:species/".
>
> Q1: The doc (https://rest.ensembl.org/documentation/info/tissues <
> https://rest.ensembl.org/documentation/info/tissues>) indicates that
> there are no required parameters but that is a mistake, right? It always
> needs the species name, correct?
>
> Q2: Can I use this endpoint with other species than human? I tried with
> ovis_aries and capra_hircus but got a funny error: "error: No EQTL adaptor
> available".
>
> Q3: About the json output, the json is a list key/value pairs, with tissue
> name being the key and value being (always?) 1. Can the value in any
> circumstance be different from 1? If not, may I ask why this specific
> design choice? Why not simply return an array of tissue names?
>
> As always, many thanks in advance, Ramiro Magno
> _______________________________________________
> Dev mailing list    Dev at ensembl.org
> Posting guidelines and subscribe/unsubscribe info:
> https://lists.ensembl.org/mailman/listinfo/dev_ensembl.org
> Ensembl Blog: http://www.ensembl.info/
>
>
> _______________________________________________
> Dev mailing list    Dev at ensembl.org
> Posting guidelines and subscribe/unsubscribe info:
> https://lists.ensembl.org/mailman/listinfo/dev_ensembl.org
> Ensembl Blog: http://www.ensembl.info/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ensembl.org/pipermail/dev_ensembl.org/attachments/20190911/fc83ccf5/attachment.html>