Skip to main content

OpenAPI 1.6.0 — Unified Base URLs & API Paths | Endpoints Added to MCP Server

Candescent Team
Candescent Team
Developer Experience Team

This release syncs the Candescent DI API reference to specification version 1.6.0. Base URLs now use dedicated Sandbox, Stage, and Production hosts, and endpoint paths are aligned to a consistent /v1/... (and /v3/... where applicable) structure instead of legacy service-prefixed routes. The introduction page, authentication examples, and generated operation topics are updated across all API categories.

You can view the OpenAPI specification in the public GitHub repository candescent-dev/openapi.

What's New​

API Reference​

  • The API specification is version 1.6.0.
  • Base URLs — Sandbox (https://api.sandbox.candescent.com), Stage (https://api.stage.candescent.com), and Production (https://api.candescent.com) replace the prior digitalbanking path-style hosts. Token and sample request examples on the Candescent DI API introduction reflect the Stage host.
  • Unified paths — Operations across Customer Management, Core Banking, Business Banking, Money Movement, Alerts And Notifications, Documents And Preferences, and Customer Campaigns now document routes such as /v1/accounts, /v1/alert-preferences, /v1/ach-payments, and /v3/groups instead of legacy prefixes.
  • Authentication — OAuth token and authenticated request examples use the updated Stage URLs; access tokens are documented with a ~24 hour lifetime.
  • Generated operation pages, schemas, and the API sidebar are refreshed to match the latest contract, including routine updates across registration, accounts, payments, alerts, disclosures, experience groups, and MX.

MCP Server​

  • A few Core Banking and User APIs can now be invoked via the newly-enabled MCP Server. Beta testing only; not for production use. FIs onboarded to the Developer Console can now test this new functionality using their API keys.

Get Started​

  1. Candescent DI API — Introduction and updated documentation (OpenAPI 1.6.0).
  2. Authentication — OAuth token APIs and authorization flows.
  3. Core Banking — Accounts, transactions, banking activities, and images.
  4. Quick Start Guide — Make your first API call with current base URLs.

The Candescent Developer Experience Team