[ensembl-dev] Ensembl REST API | GET xrefs/name/:species/:name

[Tiago Grego]

Hello Ramiro,

all_levels=1 retrieves the same type of object (DBEntry), and the best 
place to find some documentation is the Perl API page I sent before.

The difference between all_levels=1 is that it will retrieve *all* 
related DBEntries for the gene. This includes all DBEntries that are 
associated with the transcripts and corresponding translations.
If you only want to retrieve the DBEntries associated with the gene (and 
not the transcript and translations) then you must not use all_levels=1.

Best wishes,
Tiago



On 21/10/2019 13:29, Ramiro Magno wrote:
> Hi Devs,
> 
> as a follow up: where can I find the doc details about these extra 
> fields retrieved when we set the parameter all_levels=1:
> 
> 1. evalue
> 2. xref_start
> 3. xref_end
> 4. ensembl_start
> 5. ensembl_end
> 6. xref_identity
> 7. cigar_line
> 8. score
> 9. ensembl_identity
> 10. linkage_types
> 
> Example: 
> https://rest.ensembl.org/xrefs/id/ENSG00000157764?all_levels=1;content-type=application/json
> 
> Thank you. Best regards,
> 
> RM
> 
> On Mon, 21 Oct 2019 at 09:37, Ramiro Magno <ramiro.magno at gmail.com 
> <mailto:ramiro.magno at gmail.com>> wrote:
> 
>     Hi Devs,
> 
>     Given this endpoint:
>     https://rest.ensembl.org/documentation/info/xref_name
> 
>     where can I find documentation details about theeach of the fields
>     in the json response file?
> 
>     |{ "description": "", "info_type": "DIRECT", "primary_id": "15",
>     "db_display_name": "DataBase of Aberrant 3' Splice Sites",
>     "display_id": "BRCA2", "dbname": "DBASS3", "version": "1",
>     "synonyms": [], "info_text": "Generated via Database of aberrant 3'
>     splice sites." }|
> 
> 
>     Thank you. Regards,
> 
>     RM
> 
> 
> _______________________________________________
> 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/
>