Verified Runs

Verified Runs is the evidence behind the Verified badge. A Sync PR is “simple” when it just proposes a change, and “verified” when API Sync has actually built and deployed the patched code and run your test against it. This screen lists every one of those test runs across all your applications, newest first, and tells you whether each one passed.

What it does#

Counts at the top. Four tiles summarize the runs currently in view: total, passed, failed, and running.

A filter. A toggle switches between all runs, passed only, and failed only. A count next to it reports how many runs match.

One card per run. Each run shows the application it ran for, a verdict chip (Verified, Not verified, or Running), and a short summary. Below that is a line of context: which test ran, why it ran, when it finished, how long it took, and the deployment URL it hit. Two test types appear:

• Postman collection runs your collection with Newman, using the optional dataset and environment, against the deployed application.
• OpenAPI check is a smoke test that calls each parameterless GET on the deployment and asserts the status is one the spec documents.

The “why it ran” is either deploy-triggered (your pipeline called the webhook after a deploy) or manual. Runs with extra detail expand in place to show the per-request breakdown.

How it behaves#

Verdicts are earned, never assumed. A run only records “passed” or “failed” from a real execution against a real deployment. For a Postman run, passing means every request and every assertion passed. Anything that is not a clean pass is a failure, carrying the real error. There are no pass thresholds to tune, because a threshold turns a gate into a suggestion.

Runs are asynchronous and the screen keeps up. Collections can be slow, so the runner fires and forgets. This screen polls every eight seconds, so a run started elsewhere moves from Running to its verdict without a manual refresh.

How a run gets triggered. The full path is set up per application in Integration Inventory: you give API Sync a dedicated branch and a deployment URL, your pipeline deploys that branch, and it calls a signed webhook to say the deployment is live. The webhook is HMAC-signed with a per-config secret so only your pipeline can trigger a run. API Sync then runs your test against the fresh deployment.

Honest empty state. With no runs yet, the screen explains how to get one: enable Verified PR on an application, then run its test or trigger a deploy.

Data flow. The list is useListAllVerifiedPrRunsQuery over GET /v1/api-sync/verified-pr/runs, optionally filtered by status, with a 200-run limit and the eight-second poll. Per-application configuration and single-app run history live on the Integration Inventory side of the same backend module.