ParaPort Logo
Configuration

Parameters

Fields, types, and behaviour for ParaPort integration

The parameters mirror the TeleportParams<string> type from @paraport/core — numeric values are strings and are converted to bigint internally.

Fields

FieldRequiredDefaultDescription
addressUser account encoded as SS58 (ParaPort re-encodes per chain).
chainDestination parachain (see Supported Chains).
assetAsset symbol (see Supported Assets).
amountPlanck-denominated string; converted to bigint internally.
getSignerAsync function returning a PolkadotSigner.
teleportModeoptionalexpectedOne of 'expected', 'exact', 'only'.
endpointsoptionalOverride RPC endpoints per chain; falls back to curated defaults.
labeloptionalUI button label.
disabledoptionalDisables the UI button.
appearanceoptionalPer‑instance CSS variables (e.g., { '--radius': '12px' }).
themeModeoptionalauto`'light'
displayModeoptional'integrated'UI layout mode (currently only 'integrated').
ui.addFundsoptionaltrueShow/hide the manual top-up CTA.
logLeveloptional'INFO'SDK log level: `'DEBUG'

SDK-only (Vanilla)

These apply only when using @paraport/sdk directly:

FieldRequiredDefaultDescription
integratedTargetIdDOM element ID where the SDK UI mounts.

ParaPort defaults to the chains defined in SDKConfigManager.getDefaultConfig(). To narrow support, pass your own chains list when instantiating ParaPortSDK directly.

Events

Every integration surface (Vanilla SDK, Vue, React) exposes the same lifecycle callbacks:

EventSignatureDescription
onReady(session: TeleportSessionPayload) => voidUI is ready; first session payload is available.
onSubmit({ autoteleport: boolean, completed: boolean }) => voidButton clicked; pre-execution signal.
onCompleted() => voidTeleport flow finished successfully.
onAddFunds() => voidUser requested manual top-up.
← Back to Start Here