works with

Spring API Forge

Spring API Forge eliminates Swagger UI integration overhead by discovering endpoints directly from your Spring Boot source code and generating organized HTTP Forge collections for testing, documentation, and automation—without adding app dependencies or production security risks.

Start In 60 Seconds

1. Open a workspace with Spring Boot controllers.
2. Run Spring API Forge: Scan Spring Boot Endpoints.
3. Open the Spring APIs sidebar and click Open in HTTP Forge.
4. Send the request immediately with URL, params, body, and schema context prefilled.

Why Spring API Forge (vs. Swagger UI)

Why Teams Use It

• Discover Spring Boot endpoints directly from source code instead of manually curating requests.
• Open endpoints in HTTP Forge with method, path, params, headers, and body/schema context already mapped.
• Keep one API contract that can flow into testing, OpenAPI generation, QA, and automation.
• Support multi-app workspaces and refresh endpoint discovery as source changes.

Collection Generation

Use the command Spring API Forge: Generate HTTP Forge Collection from Controllers to create runnable request collections directly from discovered Spring endpoints.

Visual preview: Spring API Forge discovers endpoints, then HTTP Forge handles collection editing and execution.

• Create new: creates a fresh collection (auto-incremented name if needed).
• Replace existing: overwrites the selected existing collection with newly generated controller folders and requests.
• Append existing: keeps existing items and appends generated controller folders/requests.

Walkthrough: Generate Collection From Controllers

1. Run Spring API Forge: Generate HTTP Forge Collection from Controllers.
2. Pick the target Spring app (when multiple apps are detected).
3. Choose a mode: Create new, Replace existing, or Append existing.
4. Confirm the summary (if enabled), then Spring API Forge writes and opens the collection in HTTP Forge.

Expected result:

• Controller-based folders are created/updated.
• Requests include method/path/body/schema metadata from Spring annotations.
• Base URL variable is seeded per app (for example: myServiceBaseUrl).

By default, Spring API Forge shows a pre-save confirmation summary before writing collection changes. You can disable this for faster one-click generation by setting:

{
  "springApiTester.confirmBeforeGenerateCollection": false
}

Example Setup

To scan repositories outside the current workspace, add paths in VS Code settings:

{
  "springApiTester.additionalPaths": [
    "/home/user/projects/order-service",
    "C:\\Users\\user\\projects\\user-service"
  ],
  "springApiTester.confirmBeforeGenerateCollection": true,
  "springApiTester.largeCollectionReplaceWarningThreshold": 200,
  "springApiTester.enableGenerationTelemetryLogs": true
}

Settings Presets

Preset recommendations and full copy-ready JSON examples are in docs/settings-presets.md.

Quick summary:

• Cautious: confirmation on, lower replace warning threshold, telemetry logs on.
• Fast: confirmation off, higher replace warning threshold, telemetry logs off.
• Monorepo: add multiple service paths, confirmation on, balanced warning threshold.

Configuration

Commands

Related Links

• HTTP Forge
• HTTP Forge README
• HTTP Forge MCP Server Guide