Before a team changes an endpoint, someone has to answer a plain question: who calls this? In most companies the answer lives in people's heads, in an old wiki page, or in a Slack thread that starts after something broke.
We build Graphwake , which tells the teams that consume an API when a change in its OpenAPI spec is about to break them, so it needs that answer for every endpoint. What you're really asking about is a relationship between teams and endpoints, so we stored it as one, in a graph. It turns out to need very little: three kinds of node, three kinds of edge, and queries that are one or two hops long.
Three nodes, three edges
Node What it is Where it comes from
Service One API with its own OpenAPI spec, such as orders-api . Set up in Graphwake with its spec, from a published URL or a CI step.
Endpoint One method and path of a service, such as GET /orders/{id} . Read from the spec.…