Skip to main content

Java SDK 1.0.0, Forge CLI Console Environments & Building Extensions

This release adds a new Java SDK section (version 1.0.0) with guides for setup, your first API call, reference docs, examples, framework integration, and troubleshooting. Forge CLI guides now cover forge env switch so you can move between Sandbox, Staging, and Production console environments without logging out, plus new forge ask flags for AI-powered docs search. Building Extensions guides explain which package versions to use in the extensibility monorepo and how to install them correctly.

What's New​

Java SDK Guide​

  • Java SDK — New guides for com.candescent.forge:di-java-sdk on Maven Central. Call the Candescent DI API from Java 17+ apps.
  • Server-side SDK Overview — Shows both TypeScript SDK and Java SDK packages, with links to the cdx-typescript-sdk and cdx-java-sdk example repos.
  • Overview — How CandescentClient works with automatic OAuth, typed models, PageIterator, typed exceptions, retries, and standalone operations in com.candescent.di.operations.
  • Installation — Add the Maven or Gradle dependency, set CANDESCENT_* credentials, and run a first API call.
  • Quick Start — Create a client, authenticate with OAuth or CandescentClient.fromEnv(), and call accounts and business banking APIs.
  • SDK Reference — ClientConfig options, API areas on the client, pagination, errors via CandescentClient.mapException(), and package layout.
  • Examples — Runnable cdx-java-sdk examples for accounts, authentication, business banking, campaigns, alerts, MX, and more, plus a batch runner and a TypeScript SDK parity table.
  • Framework Integration — Use one CandescentClient in Spring Boot or serverless apps.
  • Troubleshooting — Fix missing packages, Java version issues, auth errors, hostUserId/loginId rules, and example setup.

Forge CLI​

  • Command Reference — Documents forge env switch for Sandbox, Staging, and Production, renames the SDK environment variables section so it is separate from the console environment, and updates forge login, forge status, and how you pick a console environment after MFA.
  • AI-powered docs search — forge ask interactive mode and flags (--json, --no-follow-ups, --no-sources, --session, --new-session), continue a conversation across calls, and fix auth errors and expired sessions.
  • Quick Start — Staging added to the environment table, notes that forge env switch clears app selection, and use forge ask --new-session when a docs session expires.
  • Overview — forge login signs into Production (public builds), forge env switch moves between Sandbox, Staging, and Production in the Developer Console, and forge env load / set / show / clear manage SDK credential variables separately (not the console environment).
  • Troubleshooting — Fix forge env switch errors, run forge app select after switching, recover from forge ask auth and session errors, and move %USERPROFILE%\.forge\cdx-extensibility-apps to another drive on Windows when C: is full.

Building Extensions Guide Updates​

  • Dependency versions — Overview callout and OLB integration Shared dependencies guidance point to the CDX Extensibility Apps README. Install from the repo root with the committed package-lock.json — do not upgrade packages one at a time.
  • Widgets FAQ — Version mismatch and peerDependencies answers link to the monorepo Shared dependencies section.

Get Started​

  1. Java SDK Installation — Add com.candescent.forge:di-java-sdk to your Maven project and set up credentials.
  2. Java SDK Quick Start — Create a CandescentClient and call accounts or business banking APIs.
  3. Java SDK Examples — Clone cdx-java-sdk and run examples against Stage (the SDK API environment).
  4. Forge CLI Command Reference — Run forge env switch for Sandbox, Staging, or Production, then run forge app select.
  5. Forge CLI Troubleshooting — Fix forge ask session errors or move the extensibility checkout on Windows.
  6. Building Extensions — Use the Shared dependencies versions when building widgets or mobile features.

The Candescent Developer Experience Team