Skip to content
CPQ DevKit™
Back to blog
2.6.6

CPQ DevKit™ 2.6.6: vendor API currency across Oracle, Salesforce, SAP, and Epicor

Fusion REST paths and OAuth bearer for Oracle, Salesforce API 67.0 with PKCE, live SAP global-script sync, and Epicor tenant version probes.

CPQ DevKit™ 2.6.6 brings the four VS Code extensions onto the current vendor API surfaces. The Marketplace version for each extension is 2.6.6.

Oracle CPQ

Standalone BigMachines sites still use /rest/v19. Fusion Application hosts (*.fa.*) now use /cpq/rest/v19. If the site URL already ends in /cpq, the client keeps the relative rest/v19 suffix. Set restBasePath in the project or developer configuration when a tenant uses a custom prefix.

Environments can authenticate with an OAuth access token instead of Basic username/password. Set accessToken (and optional restBasePath) on the environment; the REST client sends Authorization: Bearer when a token is present.

New project configuration and backup workflows default to REST v19 (previously v17). The bundled CLI utilities (ocpq-util, ocpq-backup) call v19 as well, or CPQ_API_VERSION when set.

The hosted Oracle MCP server accepts the same Fusion path and bearer token via X-Oracle-CPQ-Access-Token and X-Oracle-CPQ-Rest-Base-Path.

Full notes: Oracle changelog.

Salesforce CPQ

Platform API calls now use 67.0 (Summer ’26) in jsforce and the hosted MCP server.

Org sign-in uses Authorization Code + PKCE instead of the implicit grant. Sign in again after you update so the extension can exchange the authorization code. The callback still accepts a legacy fragment token if no code is present.

A new MCP tool, rca_place_sales_transaction, calls Revenue Cloud placeSalesTransaction on /services/data/v67.0/actions/standard/placeSalesTransaction.

Full notes: Salesforce changelog.

SAP CPQ

The SAP extension can pull and push global scripts against a live tenant through /api/script/v1/globalscripts. Use Pull Global Scripts from Tenant and Push Ready Changes to Tenant.

Tenant authentication tries OAuth client-credentials first, then password grant. Username is optional on the environment; the password stays in VS Code Secret Storage. After a create, the new script id is written back to the properties JSON so later pushes update the same remote script.

Epicor CPQ

Show Tenant API Version calls GET /api/version on the connected KBMax tenant. SNAP pulls log that version and warn if the probe fails.

What to do after you update

  1. Oracle Fusion tenants: confirm the site URL (or restBasePath) resolves to /cpq/rest/v19. OAuth-only environments need accessToken instead of Basic credentials.
  2. Salesforce: sign in again so PKCE can run.
  3. SAP: configure tenant credentials, then pull global scripts before your first push.
  4. Epicor: run Show Tenant API Version after you connect, or check the SNAP pull log.