POST /api/kegg/entries/links
Price: 10 credits
Follow KEGG cross-references, or convert identifiers between KEGG and an outside database
One result per source entry, with everything it points at in `targets` - so a single entry as `source` gives one result, while a whole database or organism code as `source` gives the entire mapping in one call. Use `conv` to move between KEGG and outside identifier spaces such as ncbi-geneid or uniprot, and `link` for relations inside KEGG such as gene to pathway. A pair that exists but has no links is an empty result rather than an error, while an impossible pair is rejected.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)source string required — A KEGG entry identifier, a database name or an organism code to take the links of (examples: "hsa:7157", "hsa05210", "hsa", "pathway"; minLength: 1)target string required — The database to link into: a KEGG database, or an outside database when `operation` is conv (examples: "pathway", "disease", "ncbi-geneid", "uniprot"; minLength: 2; pattern: ^[a-z0-9][a-z0-9\-]{1,20}$)operation string — `link` follows KEGG's own cross-references; `conv` converts identifiers between KEGG and an outside database (default: "link"; one of: "link", "conv"; examples: "link", "conv")count integer required — Max number of results (min: 1)@type string (default: "KeggLinkSet")id string requireddatabase string (default: "")targets array (default: [])url string (default: "")422 — KEGG does not link these two databases, or `source` is not a KEGG identifier Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.