Skip to main content

​
Notes

  • Authenticated, no credits — send the same X-API-Key header as every Tako endpoint. Graph calls consume no credits; rate limits are 180/minute and 10,000/day.
  • Use graph node to confirm what a node id actually refers to. Given an id — from a Search or Answer card, from Graph Search, or from Graph Related — resolve it here to get the node’s full name, aliases, and description and verify it’s the entity or metric you expected before you rely on it.
  • The id is the opaque public id Tako returns everywhere it exposes a node. The same id works across all graph endpoints.
This endpoint is in beta. A resolved node describes what Tako knows about that id — it does not promise that any specific entity + metric combination exists, or that data is available for it. Use Graph Related to see what a node connects to, and confirm coverage at Search or Answer.

​
Disambiguation flow

The node id is the through-line that ties search results back to the graph. A typical loop:
  1. Run a Search or Answer query and read the node ids off the card’s nodes array.
  2. Resolve each id here to confirm the card was built from the entities and metrics you meant — compare name, aliases, and label. The names themselves settle homonyms: China the country and China, TX are distinct nodes with distinct ids.
  3. If a node isn’t the one you wanted, resolve the intended one with Graph Search instead, then re-run the query pinned to that id via sources.data.node_ids.

​
Path format

The path takes the full opaque id, so URL-encode it — ids contain ::. The trailing slash is required; without it Tako responds 301 to the canonical path, which clients only follow when told to (curl -L).

​
Example response

A 404 means the id does not resolve to a node — either it’s malformed, it uses an unknown prefix, or no such node exists.