CPQ DevKit™ for Epicor

VS Code extension + Bun CLI for the Epicor CPQ OpenAPI spec you provided (KBMax REST API).

This package uses your swagger.json and supports all operations through dynamic execution by operationId (or by method + path).

Included Assets

• resources/swagger.json (copied from your provided file)
• Total discovered operations: 566
• Total discovered paths: 415

What This Package Adds

1. Bun CLI (all operations)

Run from this package folder:

cd /Users/mirceatrofimciuc/Projects/Extensions/packages/vsc-cpq-devkit-epicor

List all operations:

bun run epicor:api --list-operations

Show one operation:

bun run epicor:api --show-operation ApiAuthCurrentuserGet

Run one operation by operationId:

bun run epicor:api \
  --operation-id ApiAuthCurrentuserGet \
  --base-url https://your-epicor-cpq-host \
  --username your-user \
  --password your-pass

Run with params/body:

bun run epicor:api \
  --operation-id ApiAdminProductsByIdPut \
  --base-url https://your-epicor-cpq-host \
  --username your-user \
  --password your-pass \
  --path-params '{"id":"123"}' \
  --body '{"name":"Updated Name"}'

Dry run (no HTTP call):

bun run epicor:api --operation-id ApiAuthCurrentuserGet --base-url https://host --dry-run

2. VS Code Extension Commands

Command Palette commands:

• Configure Epicor CPQ Connection
• List Epicor CPQ API Operations
• Create Epicor CPQ Request Template
• Run Epicor CPQ Request (Active JSON)
• Run Epicor CPQ Operation (Interactive)

3. Workspace Config

The extension stores workspace connection data here:

• .cpqdevkit/epicor/epicor-config.json

Password is stored in VS Code secret storage (not in the config file).

Build

bun install
bun run build

Package

bun run package

Notes

• The OpenAPI document included here is OpenAPI 3.0.1.
• Auth is handled via Basic auth (username/password) in the client/extension request executor.
• You can override the spec path via VS Code setting epicorCpq.specPath.