Use these SDKs when you want typed request helpers, consistent authentication handling, and a faster path from proof of concept to production integration.
Available SDKs
JavaScript SDK
Browser and server-side helpers for authentication, capability calls, and embedded runtime bootstrapping.
Python SDK
Backend-friendly client for authentication, token exchange, and platform capability workflows.
Installation
- JavaScript
- Python
npm
pnpm
yarn
Quick examples
- JavaScript
- Python
What the SDKs cover
Package links
- JavaScript package: npmjs.com/package/@narrativebanking/sdk
- Python package: pypi.org/project/narrative-sdk
- Source: github.com/narrativebanking
When to use SDKs vs direct integration
Use the SDKs when you want the fastest implementation path
Use the SDKs when you want the fastest implementation path
The SDKs reduce boilerplate around auth, base URL configuration, and capability organisation.
Use direct integration when you need full transport control
Use direct integration when you need full transport control
If your environment already has a standardized HTTP abstraction, you can still integrate using your own client patterns.
You can mix both approaches
You can mix both approaches
Many teams use the hosted loader for embedded UI and use SDKs mainly for backend or service-to-service workflows.