> ## 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. # Unified API specifications > Browse the Grand Central unified API specifications across all CalVer versions Grand Central unified APIs define a vendor-neutral contract between Backbase Engagement Banking Platform and connector implementations. Each connector implements one or more of these API specifications to expose banking functionality through a consistent interface, regardless of the underlying core banking system or third-party vendor. ## Browse the API specifications Select a version to open the interactive API specification explorer on Backbase.io: * [2026.07](https://backbase.io/developers/apis?version=2026.07\&specType=unified) * [2026.06](https://backbase.io/developers/apis?version=2026.06\&specType=unified) * [2026.05](https://backbase.io/developers/apis?version=2026.05\&specType=unified) * [2026.04](https://backbase.io/developers/apis?version=2026.04\&specType=unified) * [2026.03](https://backbase.io/developers/apis?version=2026.03-LTS\&specType=unified) * [2026.02](https://backbase.io/developers/apis?version=2026.02\&specType=unified) * [2026.01](https://backbase.io/developers/apis?version=2026.01\&specType=unified) * [2025.12](https://backbase.io/developers/apis?version=2025.12\&specType=unified) * [2025.11](https://backbase.io/developers/apis?version=2025.11\&specType=unified) * [2025.10](https://backbase.io/developers/apis?version=2025.10\&specType=unified) * [2025.09](https://backbase.io/developers/apis?version=2025.09-LTS\&specType=unified) * [2025.08](https://backbase.io/developers/apis?version=2025.08\&specType=unified) * [2025.07](https://backbase.io/developers/apis?version=2025.07\&specType=unified) ## Available API domains The following API domains are available in the unified API specification. Each domain defines the contract that connectors must implement to expose the corresponding banking capability. **API**: `grandcentral-party-api` Manages the creation, retrieval, and update of party (customer and business) records. Provides the `isCustomer` flag to distinguish customer parties from non-customer parties, and supports beneficiary verification operations. Implemented by: [core banking connectors](/connectors/core-banking/overview) **API**: `grandcentral-party-lifecycle-api` Manages identity verification and customer onboarding workflows. Supports applicant creation, identity verification result retrieval, document download, customer screening against global watchlists (sanctions, PEPs, adverse media, AML), and Confirmation of Funds (CoF) consent management. Implemented by: KYC/KYB connectors ([ComplyAdvantage](/connectors/kyc-kyb/complyadvantage/overview), [Onfido](/connectors/kyc-kyb/onfido/overview), [Prove](/connectors/kyc-kyb/prove/overview)) **API**: `grandcentral-party-reference-api` Provides event-based support for receiving updates on party fields such as email address, phone number, and postal address. Enables inbound party reference connectors to keep party data synchronized. Implemented by: [core banking connectors](/connectors/core-banking/overview) (inbound) **API**: `grandcentral-payment-order-api` Manages the full payment lifecycle: initiation, validation, status retrieval, fee calculation, bank details lookup, standing orders, and scheduled payments. The v2 specification (from 2026.04) aligns with ISO 20022 standards, adding support for remittance information, regulatory reporting, FX contract tracking, and structured address formats. Implemented by: payments connectors ([OBPM](/connectors/payments/obpm/overview), [Alacriti](/connectors/payments/alacriti/overview), [SurePay](/connectors/payments/surepay/overview)) **API**: `grandcentral-batch-payment-api` Supports creating and cancelling batches of payments in a single operation. Designed for high-volume use cases such as payroll, vendor transfers, and reimbursements. Implemented by: batch payments connectors ([OBPM Batch](/connectors/payments/obpm-batch/overview), [Alacriti Batch](/connectors/payments/alacriti-batch/overview)) **API**: `grandcentral-servicing-consent-api` Manages Open Banking consent flows for Account Information Services (AIS), Payment Initiation Services (PIS), and Confirmation of Funds (CoF). Supports Berlin Group and Open Banking scheme filters for consent deletion. Implemented by: [Open Banking connectors](/connectors/open-banking/overview) (Salt Edge) **API**: `grandcentral-fraud-detection-api` Evaluates fraud risk during account opening and transaction processing. Returns risk scores, `riskIndicators` detailing matched fraud signals, and a `decisionFlag` providing the vendor-recommended action (Allow, Block, Challenge, or Quarantine). Implemented by: [fraud detection connectors](/connectors/fraud-detection/overview) ([Feedzai](/connectors/fraud-detection/feedzai/overview), [BioCatch](/connectors/fraud-detection/biocatch/overview)) **API**: `grandcentral-location-data-management-api` Provides address autocomplete and address metadata retrieval for US and international addresses. Banks use the metadata to apply their own validation logic for address input acceptance. Implemented by: address verification connectors ([Smarty](/connectors/kyc-kyb/smarty/overview)) **API**: `grandcentral-deposit-event` Provides event-based deposit account data aligned with the `grandcentral-deposit-api` specification. Enables downstream systems to receive deposit account updates through event streams. Implemented by: [core banking connectors](/connectors/core-banking/overview) ## Related topics * [Architecture and unified APIs](/architecture#unified-apis-and-bian) — how the unified API layer works and its relationship to BIAN standards * [Get started with connectors](/connectors/getting-started) — how to build a connector that implements a unified API