Graphwake maps which teams consume each endpoint of your OpenAPI specs, shows the impact before the merge, and tells only those teams in Slack, Microsoft Teams or email.
7 days with every featureNo credit cardFirst spec in minutes
v2.4.0v2.5.0GET/orders/{id}Breaking change in GET /orders/{id}
total was removed
Slack
Microsoft Teams
Email
GitHub Actions
GitLab CI
Azure DevOps
Bitbucket Pipelines
JenkinsGraphwake builds a map from your OpenAPI specs and the endpoints each team subscribes to. Before a change ships, it shows which teams it reaches and how risky it is. Afterwards, it keeps a record of every change and every decision.
DELETE /orders/{id}/legacy.| Change | Service | When | Status |
|---|---|---|---|
BreakingGET/orders/{id}total removed, currency now required | orders-apiPR #1284, merged | Today, 14:02 | |
DraftPOST/carts/{id}/checkoutcoupon becomes a required field | carts-apiPR #311, still open | Today, 10:20 | |
BreakingGET/customers/{id}address split into address_lines | customers-apiv3.1.0 | Oct 24 | Handled by Tom Becker |
Non-breakingGET/orders/{id}discounts added | orders-apiv2.4.0 | Oct 12 | No action needed |
| Service | Owner | Endpoints | Consumers | Source | Last change |
|---|---|---|---|---|---|
| orders-api | payments-team | 5 | 4 teams | GitHub Actions | Breaking, today |
| payments-api | payments-team | 18 | 6 teams | GitHub Actions | 9 days ago |
| customers-api | identity | 22 | 7 teams | URL, every 15 min | Breaking, Oct 24 |
| catalog-api | No owner | 31 | 3 teams | GitLab CI | Oct 20 |
| legacy-billing | finance | 9 | None | URL, last check failed | Aug 2 |
GitHub ActionsGitLab CIAzure DevOps| Service | Run | Result | When |
|---|---|---|---|
| orders-api | PR #1284, GitHub Actions | 3 breaking changes | 2 min ago |
| carts-api | PR #311, GitHub Actions | 1 breaking change | 4 h ago |
| catalog-api | main, GitLab CI | Nothing breaks | Yesterday |
| search-api | PR #88, GitLab CI | Spec rejected: invalid YAML | Yesterday |
| Team | Members | Owns | Consumes | Alerts go to |
|---|---|---|---|---|
| payments-team | 7 | orders-apipayments-api | 4 endpoints | Slack #payments |
| checkout | 4 | Nothing | 3 endpoints | Slack #team-checkout |
| fulfillment | 3 | PATCH/orders/{id}/status | 2 endpoints | Microsoft Teams |
| mobile-app | 6 | Nothing | 11 endpoints | Slack #mobile-alerts |
| inventory | 2 | Nothing | 1 endpoint | Slack delivery failing |
Tell consumers about a breaking change while the pull request is still open, before it merges.
Also send additions and other safe changes. Off by default, so alerts stay rare.
Send admins the endpoints that have no consumers or no owner.
Okta, connected on Oct 2.
38 people, 3 of them admins.
GET/orders/{id}checkoutmobile-appPOST/orderscheckoutGET/ordersreportingmobile-appPATCH/orders/{id}/statusowner: fulfillmentinventoryDELETE/orders/{id}/legacyNo consumers| Team | Endpoints hit | What breaks | Alert |
|---|---|---|---|
| 1mobile-app | GET/orders/{id}GET/orders | 3 breaking changes | Slack #mobile-alerts |
| 2checkout | GET/orders/{id} | total removed, currency required | Slack #team-checkout |
| 3reporting | GET/orders | page_size max lowered to 50 |
inventory consumes orders-api but none of the changed endpoints, so it isn’t pinged.
orders-api v2.5.0 merged by payments-team in PR #1284. Changed GET /orders/{id} and GET /orders.
Notified mobile-app, checkout and reporting.
Sam Rivera subscribed reporting to GET /orders.
This is why reporting heard about PR #1284.
Priya Shah made fulfillment the owner of PATCH /orders/{id}/status.
Lena Park moved mobile-app’s alerts from email to Slack #mobile-alerts.
orders-api v2.4.0 by payments-team. Added discounts to GET /orders/{id}.
Nobody was pinged: additions stay quiet.
New in this release: an impact score you can explain line by line, search that jumps to any endpoint, service or team, a weekly report on what nobody owns, and a CI agent for five pipelines.
Every pull request and spec upload gets a score from 0 to 100. Four plain rules add up to it, so a reviewer can argue with the number instead of guessing at it.
Press ⌘K anywhere in Graphwake. Endpoints open on the graph already selected, services open their graph, teams open their page.
Admins get one e-mail a week listing endpoints with no consumers and services with no owner, so the map stays honest without a clean-up project.
One step sends the spec from GitHub Actions, GitLab CI, Azure DevOps, Bitbucket Pipelines or Jenkins. If Graphwake can’t be reached, the step logs it and your pipeline carries on.
Search any endpoint across your services. Graphwake shows who owns it, which teams call it, and how far a breaking change would travel, before anyone opens the pull request.
GET/orders/{id}orders-apiPOST/ordersorders-apiGET/ordersorders-apiPATCH/orders/{id}/statusorders-apiDELETE/orders/{id}/legacyorders-apiPOST/paymentspayments-apiGET/payments/{id}/refundspayments-apiGET/customers/{id}customers-apiPOST/carts/{id}/checkoutcarts-apiGET/productscatalog-apiGET/invoices/{id}legacy-billingShowing 11 of 312 endpoints
A breaking change here sends 2 Slack messages. Last change: Breaking change today, PR #1284.
customers, legacy or catalog.New endpoints start with no subscribers, and subscriptions drift. When an endpoint is added or changed and nobody is mapped to it, Discovery reads your specs and existing subscriptions and suggests the teams it is likely to affect. One click turns a suggestion into a subscription.
POST/orders/{id}/returnsReturnRequestOrder/orders/{id} endpointsOrder schemaSubscribes to 2 other /orders/{id} endpoints and reads the Order object this one returns.
Calls GET /orders/{id} and GET /orders, both built on the same Order schema.
Owns PATCH /orders/{id}/status. A return changes an order’s status.
1 more team scored below 40% and isn’t shown. Nobody is subscribed until a team confirms.
GET/customers/{id}− address+ address_linesSubscribes to GET /customers/{id}/points, which returns the same Customer object with address in it.
Its own spec, support-api, embeds Customer.address in ticket responses.
The 6 subscribed teams were alerted. These 2 get a “this may affect you” note to confirm or dismiss.
Slack, Microsoft Teams or email: each team picks the channel it already reads. Every alert says what changed, who changed it and which endpoint you depend on.
Removed fields, new required parameters, changed types. Additions stay quiet unless you ask for them.
Your team decides which endpoints it depends on. The provider team doesn't have to keep a list.
Every version of a contract and who changed it, so the next incident review starts with facts.
orders-api changed GET /orders/{id} in pull request #1284.
total was removed from the responsecurrency is now a required query parameterGET /orders/{id}total was removed from the responsecurrency is now a required query parameterorders-api changed GET /orders/{id}, an endpoint your team subscribes to.
total was removed from the responsecurrency is now a required query parameterChanged by payments-team in pull request #1284.
Teams mark the endpoints they consume. From then on, every new version of the spec is compared with the last one and checked for anything that would break a client.
No setup on your side. Paste the address where your OpenAPI document is published; Graphwake checks it regularly and compares each new version with the previous one.
url: https://api.yourcompany.com/orders/openapi.json
owner: payments-teamA CI step sends the spec on every pull request. Consumers hear about a breaking change while it is still a review comment, not an incident.
- uses: graphwake/check@v1
with:
spec: ./openapi.yamlSomething we haven't answered? Write to us and a person replies.
Graphwake is a dependency map for your APIs. It watches your OpenAPI specs, knows which teams consume each endpoint and which team owns it, and works out who a change affects before it ships. Only the people affected by a change hear about it, and every change and decision is kept in one history.
Any team can be named the owner of a service or of a single endpoint. Ownership is optional: endpoints without an owner, or without any consumer, are flagged so someone can claim or retire them.
When an endpoint is added or changed and no team is mapped to it, Discovery compares it with the rest of your specs and subscriptions: teams that use neighbouring endpoints, endpoints that share the same schema, who owns what, and suggestions teams accepted or dismissed before. Each suggestion comes with a score and the reason behind it, from clear rules rather than a language model. A team becomes a subscriber only when someone confirms it.
oasdiff compares two OpenAPI files and finds breaking changes. Bump.sh publishes API docs and changelogs. Both answer "what changed?". Graphwake also answers "who is affected, and how badly?": consumer teams subscribe to endpoints, each pull request gets an impact score before it merges, and each breaking change is routed only to the teams that use that endpoint.
A change that can make an existing client fail: removing an endpoint or a response field, adding a required parameter or request field, changing a field's type, or narrowing the values a field accepts. Additions such as a new optional field are not breaking and stay quiet by default.
No. Graphwake only needs your OpenAPI spec. You either give us the URL where the spec is published, or a step in your CI pipeline sends the spec to us.
In Slack, Microsoft Teams or email. Each team chooses its channel, and an alert names the endpoint, what changed, who changed it and which pull request did it.
The CI agent works with GitHub Actions, GitLab CI, Azure DevOps, Bitbucket Pipelines and Jenkins. It never fails or blocks your pipeline. If you’d rather not touch CI at all, give us your spec’s URL and we check it every 30 minutes.
A flat monthly price set by the number of endpoints you watch, plus $1.99 a month for each person beyond the plan’s included users. Basic is $49 a month for up to 150 endpoints and 10 users, Pro is $119 a month for up to 500 endpoints and 30 users, and Enterprise is priced with you.
The trial lasts 7 days and includes every feature. You don’t enter a card to start. Before it ends, pick a plan from the billing page; if you don’t, the workspace closes and nobody is charged.
Nothing stops working. Alerts keep going out and every endpoint stays watched; Graphwake tells your admin it’s time to move up a plan.
Sign up with your work email, paste a spec URL or add the CI step, and invite your teams. Each team marks the endpoints it calls, and the next breaking change reaches them. Most of that fits in an afternoon.
Graphwake maps who depends on every endpoint, scores each change before it merges, and tells only the teams it breaks. Start a 7-day trial with every feature, no card needed, and see your first impact score the same day.
Graphwake maps which teams consume each endpoint of your OpenAPI specs, shows the impact before the merge, and tells only those teams in Slack, Microsoft Teams or email.
7 days with every featureNo credit cardFirst spec in minutes
v2.4.0v2.5.0GET/orders/{id}Breaking change in GET /orders/{id}
total was removed
SlackMicrosoft TeamsEmailGitHub ActionsGitLab CIAzure DevOpsBitbucket PipelinesJenkinsGraphwake builds a map from your OpenAPI specs and the endpoints each team subscribes to. Before a change ships, it shows which teams it reaches and how risky it is. Afterwards, it keeps a record of every change and every decision.
DELETE /orders/{id}/legacy.| Change | Service | When | Status |
|---|---|---|---|
BreakingGET/orders/{id}total removed, currency now required | orders-apiPR #1284, merged | Today, 14:02 | |
DraftPOST/carts/{id}/checkoutcoupon becomes a required field | carts-apiPR #311, still open | Today, 10:20 | |
BreakingGET/customers/{id}address split into address_lines | customers-apiv3.1.0 | Oct 24 | Handled by Tom Becker |
Non-breakingGET/orders/{id}discounts added | orders-apiv2.4.0 | Oct 12 | No action needed |
| Service | Owner | Endpoints | Consumers | Source | Last change |
|---|---|---|---|---|---|
| orders-api | payments-team | 5 | 4 teams | GitHub Actions | Breaking, today |
| payments-api | payments-team | 18 | 6 teams | GitHub Actions | 9 days ago |
| customers-api | identity | 22 | 7 teams | URL, every 15 min | Breaking, Oct 24 |
| catalog-api | No owner | 31 | 3 teams | GitLab CI | Oct 20 |
| legacy-billing | finance | 9 | None | URL, last check failed | Aug 2 |
GitHub ActionsGitLab CIAzure DevOps| Service | Run | Result | When |
|---|---|---|---|
| orders-api | PR #1284, GitHub Actions | 3 breaking changes | 2 min ago |
| carts-api | PR #311, GitHub Actions | 1 breaking change | 4 h ago |
| catalog-api | main, GitLab CI | Nothing breaks | Yesterday |
| search-api | PR #88, GitLab CI | Spec rejected: invalid YAML | Yesterday |
| Team | Members | Owns | Consumes | Alerts go to |
|---|---|---|---|---|
| payments-team | 7 | orders-apipayments-api | 4 endpoints | Slack #payments |
| checkout | 4 | Nothing | 3 endpoints | Slack #team-checkout |
| fulfillment | 3 | PATCH/orders/{id}/status | 2 endpoints | Microsoft Teams |
| mobile-app | 6 | Nothing | 11 endpoints | Slack #mobile-alerts |
| inventory | 2 | Nothing | 1 endpoint | Slack delivery failing |
Tell consumers about a breaking change while the pull request is still open, before it merges.
Also send additions and other safe changes. Off by default, so alerts stay rare.
Send admins the endpoints that have no consumers or no owner.
Okta, connected on Oct 2.
38 people, 3 of them admins.
GET/orders/{id}checkoutmobile-appPOST/orderscheckoutGET/ordersreportingmobile-appPATCH/orders/{id}/statusowner: fulfillmentinventoryDELETE/orders/{id}/legacyNo consumers| Team | Endpoints hit | What breaks | Alert |
|---|---|---|---|
| 1mobile-app | GET/orders/{id}GET/orders | 3 breaking changes | Slack #mobile-alerts |
| 2checkout | GET/orders/{id} | total removed, currency required | Slack #team-checkout |
| 3reporting | GET/orders | page_size max lowered to 50 |
inventory consumes orders-api but none of the changed endpoints, so it isn’t pinged.
orders-api v2.5.0 merged by payments-team in PR #1284. Changed GET /orders/{id} and GET /orders.
Notified mobile-app, checkout and reporting.
Sam Rivera subscribed reporting to GET /orders.
This is why reporting heard about PR #1284.
Priya Shah made fulfillment the owner of PATCH /orders/{id}/status.
Lena Park moved mobile-app’s alerts from email to Slack #mobile-alerts.
orders-api v2.4.0 by payments-team. Added discounts to GET /orders/{id}.
Nobody was pinged: additions stay quiet.
New in this release: an impact score you can explain line by line, search that jumps to any endpoint, service or team, a weekly report on what nobody owns, and a CI agent for five pipelines.
Every pull request and spec upload gets a score from 0 to 100. Four plain rules add up to it, so a reviewer can argue with the number instead of guessing at it.
Press ⌘K anywhere in Graphwake. Endpoints open on the graph already selected, services open their graph, teams open their page.
Admins get one e-mail a week listing endpoints with no consumers and services with no owner, so the map stays honest without a clean-up project.
One step sends the spec from GitHub Actions, GitLab CI, Azure DevOps, Bitbucket Pipelines or Jenkins. If Graphwake can’t be reached, the step logs it and your pipeline carries on.
Search any endpoint across your services. Graphwake shows who owns it, which teams call it, and how far a breaking change would travel, before anyone opens the pull request.
GET/orders/{id}orders-apiPOST/ordersorders-apiGET/ordersorders-apiPATCH/orders/{id}/statusorders-apiDELETE/orders/{id}/legacyorders-apiPOST/paymentspayments-apiGET/payments/{id}/refundspayments-apiGET/customers/{id}customers-apiPOST/carts/{id}/checkoutcarts-apiGET/productscatalog-apiGET/invoices/{id}legacy-billingShowing 11 of 312 endpoints
A breaking change here sends 2 Slack messages. Last change: Breaking change today, PR #1284.
customers, legacy or catalog.New endpoints start with no subscribers, and subscriptions drift. When an endpoint is added or changed and nobody is mapped to it, Discovery reads your specs and existing subscriptions and suggests the teams it is likely to affect. One click turns a suggestion into a subscription.
POST/orders/{id}/returnsReturnRequestOrder/orders/{id} endpointsOrder schemaSubscribes to 2 other /orders/{id} endpoints and reads the Order object this one returns.
Calls GET /orders/{id} and GET /orders, both built on the same Order schema.
Owns PATCH /orders/{id}/status. A return changes an order’s status.
1 more team scored below 40% and isn’t shown. Nobody is subscribed until a team confirms.
GET/customers/{id}− address+ address_linesSubscribes to GET /customers/{id}/points, which returns the same Customer object with address in it.
Its own spec, support-api, embeds Customer.address in ticket responses.
The 6 subscribed teams were alerted. These 2 get a “this may affect you” note to confirm or dismiss.
Each team picks the channel it already reads. Every alert says what changed, who changed it and which endpoint you depend on.
Removed fields, new required parameters, changed types. Additions stay quiet unless you ask for them.
Your team decides which endpoints it depends on. The provider team doesn't have to keep a list.
Every version of a contract and who changed it, so the next incident review starts with facts.
orders-api changed GET /orders/{id} in pull request #1284.
total was removed from the responsecurrency is now a required query parameterGET /orders/{id}total was removed from the responsecurrency is now a required query parameterorders-api changed GET /orders/{id}, an endpoint your team subscribes to.
total was removed from the responsecurrency is now a required query parameterChanged by payments-team in pull request #1284.
Teams mark the endpoints they consume. From then on, every new version of the spec is compared with the last one and checked for anything that would break a client.
Paste the address where your OpenAPI document is published. Graphwake checks it regularly and compares each new version with the previous one.
url: https://api.yourcompany.com/orders/openapi.json
owner: payments-teamA CI step sends the spec on every pull request. Consumers hear about a breaking change while it is still a review comment, not an incident.
- uses: graphwake/check@v1
with:
spec: ./openapi.yamlGraphwake is a dependency map for your APIs. It watches your OpenAPI specs, knows which teams consume each endpoint and which team owns it, and works out who a change affects before it ships. Only the people affected by a change hear about it, and every change and decision is kept in one history.
Any team can be named the owner of a service or of a single endpoint. Ownership is optional: endpoints without an owner, or without any consumer, are flagged so someone can claim or retire them.
When an endpoint is added or changed and no team is mapped to it, Discovery compares it with the rest of your specs and subscriptions: teams that use neighbouring endpoints, endpoints that share the same schema, who owns what, and suggestions teams accepted or dismissed before. Each suggestion comes with a score and the reason behind it, from clear rules rather than a language model. A team becomes a subscriber only when someone confirms it.
oasdiff compares two OpenAPI files and finds breaking changes. Bump.sh publishes API docs and changelogs. Both answer "what changed?". Graphwake also answers "who is affected, and how badly?": consumer teams subscribe to endpoints, each pull request gets an impact score before it merges, and each breaking change is routed only to the teams that use that endpoint.
A change that can make an existing client fail: removing an endpoint or a response field, adding a required parameter or request field, changing a field's type, or narrowing the values a field accepts. Additions such as a new optional field are not breaking and stay quiet by default.
No. Graphwake only needs your OpenAPI spec. You either give us the URL where the spec is published, or a step in your CI pipeline sends the spec to us.
In Slack, Microsoft Teams or email. Each team chooses its channel, and an alert names the endpoint, what changed, who changed it and which pull request did it.
The CI agent works with GitHub Actions, GitLab CI, Azure DevOps, Bitbucket Pipelines and Jenkins. It never fails or blocks your pipeline. If you’d rather not touch CI at all, give us your spec’s URL and we check it every 30 minutes.
A flat monthly price set by the number of endpoints you watch, plus $1.99 a month for each person beyond the plan’s included users. Basic is $49 a month for up to 150 endpoints and 10 users, Pro is $119 a month for up to 500 endpoints and 30 users, and Enterprise is priced with you.
The trial lasts 7 days and includes every feature. You don’t enter a card to start. Before it ends, pick a plan from the billing page; if you don’t, the workspace closes and nobody is charged.
Nothing stops working. Alerts keep going out and every endpoint stays watched; Graphwake tells your admin it’s time to move up a plan.
Sign up with your work email, paste a spec URL or add the CI step, and invite your teams. Each team marks the endpoints it calls, and the next breaking change reaches them. Most of that fits in an afternoon.
Graphwake maps who depends on every endpoint, scores each change before it merges, and tells only the teams it breaks. Start a 7-day trial with every feature, no card needed, and see your first impact score the same day.