SDKs and client integration

Use the HTTP contract with your language’s standard client, or generate a client from an exact reviewed specification. The quickstart includes cURL, Node.js and Python reads with the same actor and institution context.

Generated API clients

The core source snapshot is OpenAPI 3.0 and currently validates structurally. Some raw response schemas remain untyped and several handlers have documented source-specific behavior. Review the selected operations, supplements and error handling before generating a client. The local banking profile is a narrower separately scoped contract.

Pin the document hash, server build and generator version. Check decimal precision, dates, authentication, nullability, status/media handling and idempotency. Run actual conformance against the selected environment before publishing an SDK. No public Nucleus npm or Python SDK release is asserted by this site.

Mobile SDKs

The Product Bible defines modular iOS and Android SDKs for onboarding, accounts, payments, cards, savings, business approvals and support. Delivery uses compiled, signed modules and a qualified API version. A reference application may be delivered under the institution’s own store account and managed through Digital Banking Admin.

Obtain the actual module, supported platforms, signature, release notes, themes and integration contract from the product owner. The product target alone supplies no downloadable package or tested binary. Customer identity, device/session recovery, accessibility and complete banking state coverage require channel acceptance.

Operate a client safely

Use current grants and exact versioned payloads. Keep financial amounts as decimal values. Retain the original instruction and idempotency identity before submitting a mutation. After timeout, enquire through that identity. Handle denial and pending states explicitly, and keep credentials out of client logs and customer browser bundles.