Client SDKs
Integrate Vascular into your applications using our open-source client SDKs. Each SDK uses the same credential model — see Authentication for how API keys, app keys, and user IDs are sent on every request.
Connection overview
| SDK | Package / repo | Connects to | Port |
|---|---|---|---|
| Web / React | @vascular-io/vascular-js | Envoy | 8081 |
| React Native (web) | Same as Web / React | Envoy | 8081 |
| Flutter | vascular_flutter | Vascular Inbox, or Envoy with session token | 3000 or 8082 |
| Java (Backend) | io.vascular:vascular-java | Vascular Inbox | 3000 |
| Android (Java) | vascular-android | Vascular Inbox, or Envoy with session token | 3000 or 8082 |
| iOS (Swift) | vascular-ios | Vascular Inbox, or Envoy with session token | 3000 or 8082 |
Documented SDKs
- Authentication — API key, app key, user ID, and optional session token
- Web / React —
@vascular-io/vascular-jsinstallation and API - Flutter —
vascular_flutterinstallation and API - Java (Backend) —
vascular-javainstallation and API for server-side publishing
Quick start
- Deploy Vascular Inbox and obtain your license.
- Obtain your API key and app key by running the container with
show-creds— see Obtaining API and app keys. - Read Authentication and open the guide for your platform:
- Web or React → Web / React SDK and Envoy proxy
- Flutter → Flutter SDK
- Java backend → Java Backend SDK
Other platforms
Documentation for Android and iOS SDKs will be added here. Until then, refer to the repositories: