For teams

Graphwake for teams that call other teams’ APIs

Last checked 2026-11-113 min read

If your app calls another team’s API, you usually learn about a breaking change when your app breaks. With Graphwake you subscribe to the endpoints you call. When one of them is about to change in a breaking way, your team hears about it in its own Slack or Microsoft Teams channel, or by email, often while the change is still a pull request. Changes to endpoints you do not call, and additions that break nothing, stay out of your channel.

ExamplePull request #1284 · orders-api
#team-checkoutGraphwake in Slack

Breaking change in PR #1284

GET /orders/{id} · orders-api

Owned by payments-team

  • total was removed
  • currency is now required

Author: dana-k

orders-api3 breaking changes
  • checkoutSlack #team-checkout
  • mobile-appSlack #mobile-alerts
  • reportingEmail
  • searchquiet, not subscribed
In Graphwake: impact79/100High
A breaking change reaches only the three teams that subscribed to the endpoints it touches. search stays quiet. The impact score is in Graphwake, not in the message.
On this page
  1. The questions you can answer
  2. What reaches your channel
  3. Getting started
  4. Ask from your AI assistant
  5. When you may not need Graphwake
  6. Questions

The questions you can answer

QuestionWhere Graphwake answers it
Which endpoints does our team depend on?Your team page lists every endpoint you subscribe to, its owner and its last change.
Is anything we call about to change?API Changes lists what your team still has to handle, open pull requests included, each with its diff.
If they change this endpoint, are we hit?Every breaking change names the teams it reaches. Yours is on the list only if you call the changed endpoint.
Who do we ask about this endpoint?The owner team, on the endpoint page.
Are we missing an endpoint we call?Discovery suggests endpoints your team probably uses, with the reason, for you to confirm or dismiss.

What reaches your channel

One message per change: what changed, which of your endpoints it hits, how serious it is, and the pull request or release behind it. A new push updates the same message instead of posting again, and a pull request closed without merging sends a cancelled notice. When your team has dealt with it, mark it handled.

Exampleopenapi.yaml · before → after
− before+ after
/orders/{id}:  get:    parameters:      - name: currency        in: query        schema: { type: string }-       required: false+       required: true    responses:      "200":        description: OK        content:          application/json:            schema:              type: object              properties:                id: { type: string }-               total: { type: number }
  • BreakingNew required parameter currency
  • BreakingResponse field total removed
GET /orders/{id}reaches checkout and mobile-app
A removed response field is a breaking change. Graphwake tells the teams that subscribed to the endpoint.

Getting started

  1. Subscribe to what you call

    Pick the endpoints your app uses, with one click each. Discovery suggests the ones you may have missed.

  2. Choose your channel

    Your team’s Slack or Microsoft Teams channel, or email.

  3. Follow an endpoint yourself

    Anyone can follow a single endpoint and get its changes by email, whatever their team.

  4. Handle and move on

    Mark a change handled when your team is ready, so the list shows only what is left.

See who your next breaking change reaches.Paste a spec URL or add one CI step. 7-day free trial. Cancel before day 7 and you pay nothing.
Start free trial

Ask from your AI assistant

With Graphwake MCP connected, ask while you code. The answer comes from your team’s subscriptions, so it covers callers in every repository, not just the one open in front of you.

text
You:        What does checkout depend on?
Assistant:  → graphwake · get_team_dependencies("checkout")
            checkout uses 4 endpoints across 3 services.
            GET /orders/{id}       open PR #1284 breaks it
            POST /orders           no changes
            GET /customers/{id}    changed Nov 4
Example. Team, endpoint and counts are made up.

More questions to ask, and how to connect it: ask your AI assistant who an API change breaks.

Note

When you may not need Graphwake

  • You own every API you call. You already see every change before it ships.
  • The team behind the API has no OpenAPI spec. Graphwake reads specs; ask them to publish one first.

Questions

Will we get an alert for every API change?

No. Alerts are for breaking changes to the endpoints your team subscribes to. Additions and changes to other endpoints stay quiet.

Does the team that owns the API have to do anything?

They connect their spec once, by URL or with one CI step. They do not keep a list of who calls them; your subscriptions are that list.

Can I follow an endpoint on my own?

Yes. Anyone can follow a single endpoint and get its changes by email, in addition to their team’s channel.

Pick an endpoint. See who it reaches. 7-day free trial. Cancel before day 7 and you pay nothing.

Start free trial