Module api 

Current Blokli client API. Versioned Blokli API traits, selectors, aliases, and response models.

Most applications can import the common items directly from the crate root:

use blokli_client::{BlokliClient, BlokliClientConfig, BlokliQueryClient};

This module keeps the underlying versioned API available for callers that want to be explicit about the Blokli schema version they are targeting. The current public API is v1.

What lives here

• BlokliQueryClient for one-shot GraphQL queries.
• BlokliSubscriptionClient for SSE-backed GraphQL subscriptions.
• BlokliTransactionClient for signed transaction submission and tracking.
• Selectors such as AccountSelector, ChannelSelector, SafeSelector, ServiceSelector, and TicketSelector.
• GraphQL response models under types.

Address-like values are byte-array aliases such as ChainAddress, ChannelId, PacketKey, and TxReceipt. GraphQL fields that are naturally decimal or hex strings remain represented by the generated response model types under types.

Re-exports

pub use v1::AccountSelector;

pub use v1::BlokliQueryClient;

pub use v1::BlokliSubscriptionClient;

pub use v1::BlokliTransactionClient;

pub use v1::ChainAddress;

pub use v1::ChannelFilter;

pub use v1::ChannelId;

pub use v1::ChannelSelector;

pub use v1::KeyId;

pub use v1::ModulePredictionInput;

pub use v1::PacketKey;

pub use v1::RedeemedStatsSelector;

pub use v1::SafeSelector;

pub use v1::ServiceSelector;

pub use v1::ServiceTypeId;

pub use v1::TicketSelector;

pub use v1::TxId;

pub use v1::TxReceipt;

pub use v1::types;

Modules

v1

Blokli API v1 client contract.

Constants

VERSION