ArchSync
PricingDocsAboutContact
Sign inOpen the canvas
← all guides

Catch API breaks between an Express backend and a Flutter app

Your Flutter app calls the Express API with hard-coded paths and expects certain fields back. Rename a route or drop a field in the backend and nothing fails until a user opens that screen. ArchSync reads both repos and matches every call in the app to the route that answers it.

1. Put the repos side by side

Clone them into one folder. Nothing is linked or uploaded; ArchSync only reads the files.

my-product/
├─ backend/      # Express (JS or TS)
└─ app/          # Flutter

2. Scan them together

cd my-product
npx archsync scan --workspace

What ArchSync reads:

  • Backend: Express routes with their mount prefixes (app.use("/v1", router), nested routers), middleware, controllers, services and models (Mongoose, Prisma, Sequelize).
  • App: Screens and the HTTP calls they make with the http package or Dio — including base URLs and path constants defined elsewhere in the project — plus the model classes they parse responses into.

3. Read the broken calls

Every call that no route answers any more is listed with its repo, method and path. Example output:

$ npx archsync scan --workspace
  Cross-system:    68

─── Broken cross-system calls (2) ───
  ✖ app: GET /routes/user/${id}
  ✖ app: POST /points/redeem

Change something — rename a route, change a method, drop a field — and scan again to see exactly which callers it breaks. Open the result on a canvas with npx archsync serve.

4. Run it on every pull request

# CI (free): check out the related repos side by side, then scan them together
git clone --depth 1 $BACKEND_REPO backend
git clone --depth 1 $APP_REPO app
npx archsync scan --workspace     # prints "Broken cross-system calls" in the job log

With ArchSync Team, each repo pushes its map to your own Supabase, and any repo can check itself against all the others:

# CI (Team): compare this repo with what every other repo pushed
npx archsync scan
npx archsync diff --merged --json > merged.json
test "$(jq .breakingCount merged.json)" = 0   # fail the job on a breaking change

Good to know

A URL built entirely at runtime (for example read from a server response) is shown as a gap rather than guessed.

Quickstart
archsync
ArchSync

Reads every repo your product is made of and shows where they call each other — so a change on one side doesn’t surprise the other.

Product

Open the canvasPricingDocsCLI on npm

Developers

QuickstartGuides by stackCLI referenceDatabase setupReport an issue

Company

AboutContactTermsPrivacyRefundsShipping & delivery
© 2026 ArchSync · operated by Vivek Parida, Bhubaneswar, Odisha, IndiaYour code stays on your machine. Your schema lives in your database.