> ## Documentation Index
> Fetch the complete documentation index at: https://grandcentral.backbase.io/llms.txt
> Use this file to discover all available pages before exploring further.
# 2026.05
> Grand Central Unified APIs release notes, version 2026.05.
## Features
The following feature updates are available in 2026.05 for Grand Central Unified APIs:
| Product group | Software component | Version | Title | Description |
| --------------- | ---------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Activity | `grandcentral-activity-api` | 1.0.2 | Added the Grand Central Activity API for importing and syncing activities from third-party CRM portals | The `grandcentral-activity-api` provides a unified API for relationship management portals to import and synchronize activities from third-party CRM systems. The API supports creating, searching, and updating individual activity records, as well as submitting activities in bulk. |
| Correspondence | `grandcentral-correspondence-api` | 1.0.0 | Added support to receive push notifications from a digital signing vendor | Grand Central can now receive real-time notifications when a signer completes, declines, or views a document, or when the overall signature request status changes. |
| Correspondence | `grandcentral-correspondence-api` | 1.0.0 | Added the Grand Central Correspondence API for initiating document signing workflows and creating signing sessions | The `grandcentral-correspondence-api` provides two endpoints for managing digital signature workflows. `POST /documents/signature` initiates a signing workflow by uploading or referencing a document and defining recipients. `POST /sign-documents/signing-sessions` generates a signing session URL for a specific recipient, supporting embedded signing flows. Supported signature types are Simple eSignature (SES) and Advanced eSignature (AES), in both embedded and non-embedded variants. |
| Deposit | `grandcentral-deposit-api` | 1.1.0 | Added `partyRole` to account parties in the Grand Central Deposit API | The Grand Central Deposit API lets banks classify each account party's role using the `partyRole` field in the `accountParty` schema. Supported values include `OWNER`, `GUARANTOR`, and `BENEFICIARY`. |
| Deposit | `grandcentral-deposit-api` | 1.1.0 | Added debit card issuance and linking endpoints to the Grand Central Deposit API | The `grandcentral-deposit-api` now includes two endpoints for managing debit card-to-deposit account relationships. `POST /deposits/debitcard/issue` issues a new debit card and links it to a single deposit account. `POST /deposits/debitcards` links multiple existing debit cards to deposit accounts in a single request. |
| Loan | `grandcentral-loan-api` | 1.2.0 | Added repayment simulation and initiation to the Grand Central Loan API | The Grand Central Loan API supports two new repayment endpoints. `POST /loans/repayment-calculation` simulates a loan repayment for partial or full repayment, so bankers and customers can evaluate options before committing. `POST /loans/repayment` initiates the actual repayment. |
| Loan | `grandcentral-loan-api` | 1.2.0 | Added `partyRole` to account parties in the Grand Central Loan API | The Grand Central Loan API lets banks classify each account party's role in a loan relationship using the `partyRole` field in the `accountParty` schema. Supported values include `OWNER`, `GUARANTOR`, and `APPLICANT`. |
| Party Reference | `grandcentral-party-reference-api` | 2.2.1 | Added `unitNumber` to postal address in the Grand Central Party Reference API | The Grand Central Party Reference API lets banks store unit or apartment numbers as part of a party's postal address using the `unitNumber` field, aligned with ISO 20022 standards. |
## Fixes
2026.05 contains the following bug fixes for Grand Central Unified APIs:
| Product group | Software component | Version | Title | Description |
| ------------- | -------------------------------- | ------- | -------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Activity | `grandcentral-activity-api` | 1.0.2 | Fixed Activity Event schema alignment in the Grand Central Activity API | The Grand Central Activity API specification aligns with the Activity Event schema. Pagination fields match the Party Reference search API structure, and extra attributes from another schema are removed. |
| Deposit | `grandcentral-deposit-api` | 1.1.0 | MAINT-41780: Fixed `depositIds` query parameters exceeding HTTP header size limits in the Deposit Balances API | The `depositIds` query parameter in the `GET /deposits/balances` endpoint now uses comma-separated serialization (`depositIds=id1,id2,id3`) instead of repeated parameters (`depositIds=id1&depositIds=id2`). This prevents HTTP header size limit errors when fetching balances for large numbers of deposit accounts. Both serialization styles continue to be accepted, so existing consumers are not affected. |
| Loan | `grandcentral-loan-api` | 1.2.0 | MAINT-41780: Fixed `loanIds` query parameters exceeding HTTP header size limits in the Loan Balances API | The `loanIds` query parameter in the `GET /loans/balances` endpoint now uses comma-separated serialization (`loanIds=id1,id2,id3`) instead of repeated parameters (`loanIds=id1&loanIds=id2`). This prevents HTTP header size limit errors when fetching balances for large numbers of loan accounts. Both serialization styles continue to be accepted, so existing consumers are not affected. |
| Payment | `grandcentral-payment-order-api` | 2.0.2 | Fixed response descriptions, field constraints, and missing properties in the v2 Payment Order API | The 200 response descriptions for `POST /payments/fetch-fees` and `POST /bank-payment-calendar/search` show the correct status text. The `paymentInformationResponse.exchangeRate` object includes the missing rate property, `instructionId` enforces a `maxLength` of 36 (corrected from 35), and `addressType` is optional in the reusable address schema. The `paymentMechanismType` and `paymentType` descriptions no longer reference "Berlin Group". |