<div dir="ltr">Hi Julie,<br><div><br></div><div>With regards to cytobands retrieval using the Ensembl REST API, I have in the past written a short R script for that:</div><div><br></div><div><a href="https://github.com/ramiromagno/gwasrapidd/blob/master/data-raw/cytogenetic_bands.R">https://github.com/ramiromagno/gwasrapidd/blob/master/data-raw/cytogenetic_bands.R</a></div><div><br></div><div>This is the tidy dataset generated: <a href="https://github.com/ramiromagno/gwasrapidd/blob/master/data-raw/cytogenetic_bands.csv">https://github.com/ramiromagno/gwasrapidd/blob/master/data-raw/cytogenetic_bands.csv</a></div><div><br></div><div>Regards,</div><div>Ramiro</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 7 Nov 2019 at 09:18, mag <<a href="mailto:mr6@ebi.ac.uk">mr6@ebi.ac.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
Hi Julie,<br>
<br>
The /info/assembly endpoints can provide cytoband information, for
example <a href="http://rest.ensembl.org/info/assembly/homo_sapiens/X?content-type=application/json;bands=1" target="_blank">http://rest.ensembl.org/info/assembly/homo_sapiens/X?content-type=application/json;bands=1</a><br>
<br>
Sift and Polyphen scores are provided by default on all the VEP
endpoints, for example <a href="http://rest.ensembl.org/vep/human/id/rs56116432?content-type=application/json" target="_blank">http://rest.ensembl.org/vep/human/id/rs56116432?content-type=application/json</a><br>
as well as on the /overlap/translation endpoint when variants are
requested, for example <a href="http://rest.ensembl.org/overlap/translation/ENSP00000288602?type=missense_variant;content-type=application/json;feature=transcript_variation" target="_blank">http://rest.ensembl.org/overlap/translation/ENSP00000288602?type=missense_variant;content-type=application/json;feature=transcript_variation</a><br>
<br>
It is usually worth running a basic search on the main page,
<a href="http://rest.ensembl.org" target="_blank">rest.ensembl.org</a>, as it can help find the data you are looking for.<br>
<br>
In general, we are always happy to look into providing more of our
data via the REST API. <br>
Additionally, we are working on a new version of the REST API. While
some data might not be easily made available through the current
REST API, if you let us know what data you want and how you are
planning on using it, we can use this to drive our future REST API.<br>
<br>
<br>
Regards,<br>
Magali<br>
<br>
<div>On 06/11/2019 10:09, Julie Sullivan
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_default" style="font-family:"trebuchet ms",sans-serif;font-size:small">Hi Ensembl friends,</div>
<div class="gmail_default" style="font-family:"trebuchet ms",sans-serif;font-size:small"><br>
</div>
<div class="gmail_default" style="font-family:"trebuchet ms",sans-serif;font-size:small">I've been really enjoying using
the REST API, but I don't think it has all the data I need.
(e.g. cytobands, sift/polyphen scores)</div>
<div class="gmail_default" style="font-family:"trebuchet ms",sans-serif;font-size:small"><br>
</div>
<div class="gmail_default" style="font-family:"trebuchet ms",sans-serif;font-size:small">I see a changelog on github but
not a roadmap. Can you tell me if these data are likely to be
added to the data available via REST? (or if the data is there
and I've missed it!!) <br>
</div>
<div class="gmail_default" style="font-family:"trebuchet ms",sans-serif;font-size:small"><br>
</div>
<div class="gmail_default" style="font-family:"trebuchet ms",sans-serif;font-size:small">In general, are the plans to
expand the offerings of the REST API?<br>
<br>
</div>
<div class="gmail_default" style="font-family:"trebuchet ms",sans-serif;font-size:small">Thanks so much!<br>
</div>
<div class="gmail_default" style="font-family:"trebuchet ms",sans-serif;font-size:small">Julie<br>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Dev mailing list <a href="mailto:Dev@ensembl.org" target="_blank">Dev@ensembl.org</a>
Posting guidelines and subscribe/unsubscribe info: <a href="https://lists.ensembl.org/mailman/listinfo/dev_ensembl.org" target="_blank">https://lists.ensembl.org/mailman/listinfo/dev_ensembl.org</a>
Ensembl Blog: <a href="http://www.ensembl.info/" target="_blank">http://www.ensembl.info/</a>
</pre>
</blockquote>
<br>
</div>
_______________________________________________<br>
Dev mailing list <a href="mailto:Dev@ensembl.org" target="_blank">Dev@ensembl.org</a><br>
Posting guidelines and subscribe/unsubscribe info: <a href="https://lists.ensembl.org/mailman/listinfo/dev_ensembl.org" rel="noreferrer" target="_blank">https://lists.ensembl.org/mailman/listinfo/dev_ensembl.org</a><br>
Ensembl Blog: <a href="http://www.ensembl.info/" rel="noreferrer" target="_blank">http://www.ensembl.info/</a><br>
</blockquote></div>