All monitored APIs

Email

Postmark API breaking changes, mapped to your GitHub repos

Versionly monitors the Postmark API (postmarkapp.com) in the Email catalog. When Postmark ships an OpenAPI or changelog change, we find call sites in the repositories you connect and open a reviewable auto-fix pull request.

What breaks without monitoring

  • Postmark request or response fields can rename without a compile error
  • Email SDK method signatures drift between Postmark releases
  • Calls to postmarkapp.com can change auth, versioning, or payload shape

How Versionly helps

  • Catalog monitoring for Postmark (postmarkapp.com)
  • Import and host detection for Postmark usage in connected repos
  • File-level impact mapping and reviewable GitHub pull requests

Postmark + Versionly — FAQ

Does Versionly auto-merge Postmark upgrades?
No. Versionly opens a pull request when Postmark API changes hit your connected repos. Your team reviews and merges.
How does Versionly detect Postmark usage?
The catalog entry for Postmark matches SDK imports, package names, and typical postmarkapp.com hosts in the repositories you choose to connect.
See the full four-step workflow

Next step

Connect one repo. Review the first pull request.

Start with the project that talks to payments or an LLM vendor. If the PR looks wrong, close it. Versionly does not merge.

Create workspaceSDK & MCP docs