IO Wallet SDK
    Preparing search index...

    Interface FetchAuthorizationRequestOptions

    interface FetchAuthorizationRequestOptions {
        authorizeRequestUrl: string;
        callbacks: Pick<CallbackContext, "fetch">;
        walletMetadata?: {
            authorization_endpoint?: string;
            client_id_prefixes_supported?: string[];
            request_object_signing_alg_values_supported?: string[];
            response_modes_supported?: string[];
            response_types_supported?: string[];
            vp_formats_supported?: Record<string, unknown>;
        };
        walletNonce?: string;
        x509Certificate?: {
            binding: X509CertificateBinding;
            leafCertificate: string;
        };
    }
    Index

    Properties

    authorizeRequestUrl: string

    The authorization URL from the QR code Should contain client_id and either request or request_uri query parameters

    callbacks: Pick<CallbackContext, "fetch">

    Callback functions for making HTTP requests Allows for custom fetch implementation

    walletMetadata?: {
        authorization_endpoint?: string;
        client_id_prefixes_supported?: string[];
        request_object_signing_alg_values_supported?: string[];
        response_modes_supported?: string[];
        response_types_supported?: string[];
        vp_formats_supported?: Record<string, unknown>;
    }

    Optional wallet metadata to send when request_uri_method=post. If not provided and POST is required, sends an empty body (basic implementation).

    Specification: IT-Wallet v1.3.3 recommends (SHOULD) sending wallet capabilities in application/x-www-form-urlencoded format when using POST.

    walletNonce?: string

    Optional wallet nonce for replay attack prevention (RECOMMENDED per spec)

    x509Certificate?: { binding: X509CertificateBinding; leafCertificate: string }

    Optional RP certificate context used to bind request_uri to the certificate SAN entries.