Documentation
    Preparing search index...

    Interface ActionConfiguration

    Modal / notification behavior for action calls (sendTransaction, signData, signMessage) and the return strategy applied to outgoing deep links.

    Pass on TonConnectUiOptions.actionsConfiguration (applies to every action) or on the per-call options of a single action.

    interface ActionConfiguration {
        modals?: ("error" | "before" | "success")[] | "all";
        notifications?: ("error" | "before" | "success")[] | "all";
        returnStrategy?: ReturnStrategy;
        skipRedirectToWallet?: "ios" | "always" | "never";
        twaReturnUrl?: `${string}://${string}`;
    }
    Index

    Properties

    modals?: ("error" | "before" | "success")[] | "all"

    Which lifecycle stages render a modal. 'all' is shorthand for ['before', 'success', 'error']. The "before" modal shows when the user is sent to the wallet; "success" / "error" render after the wallet replies.

    ['before']
    
    notifications?: ("error" | "before" | "success")[] | "all"

    Which lifecycle stages emit a toast notification. 'all' is shorthand for ['before', 'success', 'error'].

    'all'
    
    returnStrategy?: ReturnStrategy

    Where the wallet should send the user after they approve or decline. See ReturnStrategy'back' returns to the originating app, 'none' does nothing, a custom protocol://... opens that URL.

    'back'
    
    skipRedirectToWallet?: "ios" | "always" | "never"

    The SDK now detects the right behavior automatically for TWA-TWA connections; setting this has no effect.

    twaReturnUrl?: `${string}://${string}`

    Return target used when the dApp is itself a TWA and the connected wallet is also a TWA. The native back jump does not work across TWAs, so the dApp must pass an explicit link to come back to.

    Falls back to returnStrategy when the wallet is not a TMA.