API Contract Workbench | HTF

Spot API changes.
Release with clear evidence.

Bring contract review and repeatable API checks into the same place you write code. Understand what changed, decide what to test and keep a useful record of the result.

In development. Planned $35 per user per year. No public download or Marketplace listing yet.

Illustrated workflow from contract changes through reviewed checks to release evidence
Original workflow illustration, not an application screenshot.
Platform
JetBrains IDEs
Built for
API developers and test teams
Planned price
$35 per user per year

Keep the next change understandable.

API changes can leave tests and release notes out of step. The development workflow connects the contract, the checks you review and the evidence you keep, with accessible annual pricing.

Review the contract

The development engine reads OpenAPI JSON and YAML and highlights selected changes, including removed operations and new required inputs.

Prepare repeatable checks

Generate a draft suite from a contract or import supported Postman requests. Draft cases stay disabled until reviewed. Run explicit HTTP checks against an environment you choose.

Keep useful evidence

Save a local result record with input revisions, outcomes and response hashes. Input changes mark the current result as stale so it can be rerun.

See what a clearer handover looks like.

Explore fictional API changes, inspect saved check exports and read a genuine recorded development result. Follow the three steps, filter the findings and download the sample files.

Browser sample using genuine saved development outputs. It does not run the IDE plugin or send API test requests.

A tested workflow, with release work ahead.

A development build has been tested inside IntelliJ IDEA: contract review, reviewed HTTP checks, generated-check updates that preserve authored work, local environments, saved-result comparison, gRPC and GraphQL. The sample shows genuine outputs from that earlier tested workflow.

  • New additions: reviewed collection imports, selective updates and bounded local request/response validation pass automated and command-line checks. These newer additions still need native IDE acceptance. Authentication has partial native testing; persistence and wider provider checks remain open.
  • Clear scope: selected contract-change rules and supported import/validation subsets are covered. Imported requests need review; Postman scripts stay inactive source data. GraphQL schema validation, broader authentication flows and additional compatibility rules remain planned.
  • Before release: broader native usability, accessibility, compatibility, credential handling, security, dependency review and paid licensing acceptance remain open. The product is not submitted. Planned price: $35 per user per year; final scope and pricing will be confirmed before launch.
Data and requests

The current development build processes contract and suite files locally. An explicit test run sends requests to the origin you choose. It has no HTF cloud backend or AI processing. Local evidence stores outcomes and response hashes, not response bodies or request headers.

Credential provider and persistence acceptance, security review and the final data disclosure remain open. This page follows the website privacy notice.

Development enquiries

Contact apifymcpfactory@gmail.com with the product name and a description using sample data. Do not send passwords, tokens or private API data. No payment is available on this website.