API Dependency Map

See which APIs run before and after an API, which use its values, and how we know.
Updated

What It Does

A dependency map answers the question every change starts with: what else will this touch? The Dependencies tab of an API page draws the APIs that run before and after it, the ones that use its values and the ones it calls. Links come from several kinds of evidence, and the strongest one wins when a link is known in more than one way: set in a workflow, then seen happening, then stated by a person, then suggested by AI and accepted, then guessed from the paths. Links seen happening come from HAR files, live captures, gateway routes and traces, which are Discovery sources, so they appear when you have connected those. An environment filter stops a link observed in one environment from looking like it applies to all of them. Blast radius follows values and calls, not run order, so you see what a change could reach. For MCP tools, the protocol does not say which APIs a tool calls, so a person records it and the map labels the link as a person's statement that nothing has checked. The project-wide Dependencies view sits in Discovery and needs the add-on. Mock the dependencies can read the map and draft mocks of the APIs an API calls or needs first; they are created switched off and answer nothing until a person publishes them. The map is read-only.

A map of five Orders-area APIs joined by links in different colours and line styles; a legend explains Runs after, Uses a value from and Calls, and Set in a workflow, Seen happening, A person said so and Guessed from the paths; a dashed guessed link is hidden by default, and changing one API highlights what it could reach

Overview

Before you change an API, find out who relies on it. The dependency map shows which APIs run before and after an API, which use its values and which it calls. Each link says two separate things: what it means (Runs after, Uses a value from, Calls, Looks like one resource) and how we know (Set in a workflow, Seen happening, A person said so, Suggested by AI and confirmed by a person, or Guessed from the paths). A guess is never drawn as observed, and guesses stay hidden until you choose to show them. Three lenses switch between End-to-end workflows, Functional dependencies and Both, and the map opens full screen. The Dependencies tab on every API page is in all plans.

Key Capabilities

Runs after, Uses a value from, Calls and Looks like one resource, each with its own colour
Every link says how we know: set in a workflow, seen happening, a person said so, suggested by AI and confirmed, or guessed from the paths
Guesses from the paths are hidden by default and never shown as observed
Three lenses: End-to-end workflows, Functional dependencies and Both; switching never moves a card
Blast radius follows values and calls up to four hops out
Full-screen map; hover for a detail card and click to pin it
For MCP tools, a person states which APIs a tool calls and the link is labelled that way
"Mock the dependencies" drafts switched-off mocks for the APIs an API calls or needs first

How It Works

  1. 1

    Open an API and choose its Dependencies tab

  2. 2

    Pick a lens: End-to-end workflows, Functional dependencies or Both

  3. 3

    Hover a link to read the sentence and every way it is known; click to pin it

  4. 4

    Tick "Show the guesses from the paths" if you want the weakest evidence too

  5. 5

    Open the map full screen, or follow one workflow to see its steps numbered

Available on

All Plans

Included in the free trial — no credit card required.

Included in all plans on each API's Dependencies tab. The project-wide view in Discovery, and links seen in captures, gateways and traces, need the API Discovery add-on.
See pricing →

Try API Dependencies Today

Start your 15-day free trial — no credit card required.