togoid_convertId
Convert biological database identifiers by specifying a source-target route, e.g., ncbigene to uniprot.
Instructions
Convert identifiers from one database to another.
Maps IDs between biological databases — e.g., NCBI Gene IDs to UniProt accessions, or UniProt accessions to PDB structure IDs.
IMPORTANT WORKFLOW: 1. First call getAllRelation() or getRelation() to verify the conversion route exists 2. Optionally call countId() to check how many IDs will convert 3. Then call convertId() with your IDs
Args: ids: Source IDs. Accepts either a list of strings (e.g., ["672", "675", "7157"]) or a comma-separated string ("672,675,7157"). Examples: "672,675,7157" (NCBI Gene IDs), "P38398,P04637" (UniProt) route: Comma-separated pair of dataset keys: 'source,target'. Examples: - 'ncbigene,uniprot' (Gene → Protein) - 'uniprot,pdb' (Protein → 3D Structure) - 'ncbigene,ensembl_gene' (NCBI Gene → Ensembl Gene) - 'chembl_target,uniprot' (Drug Target → Protein) - 'uniprot,chembl_target' (Protein → Drug Target) - 'ncbigene,hgnc' (Gene → HGNC symbol) Multi-hop routes are also supported: - 'ncbigene,uniprot,pdb' (Gene → Protein → Structure) limit: Maximum number of results (default 10000) offset: Pagination offset for large result sets
Returns: JSON string: a bare array of [source_id, target_id] pairs. Example: '[["672", "P38398"], ["675", "O15129"]]'
Common use cases: - Bridging databases on different SPARQL endpoints - Mapping gene IDs to protein accessions for UniProt SPARQL queries - Finding PDB structures for a set of proteins - Identifying ChEMBL drug targets for a list of genes
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ids | Yes | ||
| limit | No | ||
| route | Yes | ||
| offset | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |