Expand description
A high-level, batteries-included Matrix client library written in Rust.
This crate seeks to be a general-purpose library for writing software using the Matrix Client-Server API to communicate with a Matrix homeserver. If you’re writing a typical Matrix client or bot, this is likely the crate you need.
However, the crate is designed in a modular way and depends on several other lower-level crates. If you’re attempting something more custom, you might be interested in these:
matrix_sdk_base
: A no-network-IO client state machine which can be used to embed a Matrix client into an existing network stack or to build a new Matrix client library on top.matrix_sdk_crypto
: A no-network-IO encryption state machine which can be used to add Matrix E2EE support into an existing client or library.
§Getting started
The central component you’ll be interacting with is the Client
. A basic use
case will include instantiating the client, logging in as a user, registering
some event handlers and then syncing.
This is demonstrated in the example below.
use matrix_sdk::{
Client, config::SyncSettings,
ruma::{user_id, events::room::message::SyncRoomMessageEvent},
};
#[tokio::main]
async fn main() -> anyhow::Result<()> {
let alice = user_id!("@alice:example.org");
let client = Client::builder().server_name(alice.server_name()).build().await?;
// First we need to log in.
client.matrix_auth().login_username(alice, "password").send().await?;
client.add_event_handler(|ev: SyncRoomMessageEvent| async move {
println!("Received a message {:?}", ev);
});
// Syncing is important to synchronize the client state with the server.
// This method will never return unless there is an error.
client.sync(SyncSettings::default()).await?;
Ok(())
}
More examples can be found in the examples directory.
§Crate Feature Flags
The following crate feature flags are available:
Feature | Default | Description |
---|---|---|
anyhow | No | Better logging for event handlers that return anyhow::Result |
e2e-encryption | Yes | End-to-end encryption (E2EE) support |
eyre | No | Better logging for event handlers that return eyre::Result |
js | No | Enables JavaScript API usage on WASM (does nothing on other targets) |
markdown | No | Support for sending Markdown-formatted messages |
qrcode | Yes | QR code verification support |
sqlite | Yes | Persistent storage of state and E2EE data (optionally, if feature e2e-encryption is enabled), via SQLite available on system |
bundled-sqlite | No | Persistent storage of state and E2EE data (optionally, if feature e2e-encryption is enabled), via SQLite compiled and bundled with the binary |
indexeddb | No | Persistent storage of state and E2EE data (optionally, if feature e2e-encryption is enabled) for browsers, via IndexedDB |
socks | No | SOCKS support in the default HTTP client, reqwest |
sso-login | No | Support for SSO login with a local HTTP server |
§Enabling logging
Users of the matrix-sdk crate can enable log output by depending on the
tracing-subscriber
crate and including the following line in their
application (e.g. at the start of main
):
tracing_subscriber::fmt::init();
The log output is controlled via the RUST_LOG
environment variable by
setting it to one of the error
, warn
, info
, debug
or trace
levels.
The output is printed to stdout.
The RUST_LOG
variable also supports a more advanced syntax for filtering
log output more precisely, for instance with crate-level granularity. For
more information on this, check out the tracing_subscriber documentation.
Re-exports§
pub use authentication::AuthApi;
pub use authentication::AuthSession;
pub use authentication::SessionTokens;
pub use media::Media;
pub use pusher::Pusher;
pub use room::Room;
pub use sliding_sync::SlidingSync;
experimental-sliding-sync
pub use sliding_sync::SlidingSyncBuilder;
experimental-sliding-sync
pub use sliding_sync::SlidingSyncList;
experimental-sliding-sync
pub use sliding_sync::SlidingSyncListBuilder;
experimental-sliding-sync
pub use sliding_sync::SlidingSyncListLoadingState;
experimental-sliding-sync
pub use sliding_sync::SlidingSyncMode;
experimental-sliding-sync
pub use sliding_sync::SlidingSyncRoom;
experimental-sliding-sync
pub use sliding_sync::UpdateSummary;
experimental-sliding-sync
pub use bytes;
pub use matrix_sdk_base::crypto;
e2e-encryption
pub use reqwest;
Modules§
- Types and traits for attachments.
- Types and functions related to authentication in Matrix.
- Configuration to change the behaviour of the
Client
. - Helpers for creating
std::fmt::Debug
implementations. - SDK-specific variations of response types from Ruma.
- encryption
e2e-encryption
End-to-end encryption related types - The event cache is an abstraction layer, sitting between the Rust SDK and a final client, that acts as a global observer of all the rooms, gathering and inferring some extra useful information about each room. In particular, this doesn’t require subscribing to a specific room to get access to this information.
- Types and traits related for event handlers. For usage, see
Client::add_event_handler
. - Abstraction over an executor so we can spawn tasks under WASM the same way we do usually.
- A TTL cache which can be used to time out repeated operations that might experience intermittent failures.
- Named futures returned from methods on types in the crate root.
- A linked chunk is the underlying data structure that holds all events.
- Types to interact with the native Matrix authentication API.
- High-level media API.
- High-level push notification settings API
- High-level pusher API.
- High-level room API
- Types for searching the public room directory.
- Preview of a room, whether we’ve joined it/left it/been invited to it, or not.
- Types and traits for working with the Matrix protocol.
- A send queue facility to serializing queuing and sending of messages.
- sliding_
sync experimental-sliding-sync
Sliding Sync Client implementation of MSC3575 & extensions - Collection of small helpers that implement store-based locks.
- The SDK’s representation of the result of a
/sync
request. - Utility types and traits.
Macros§
- Macro to create a RAII timer that will log a
tracing
event once it’s dropped.
Structs§
- A high-level API to manage the client owner’s account.
- The underlying room data structure collecting state for joined, left and invited rooms.
- A member of a room.
- An async/await enabled Matrix client.
- Builder that allows creating and configuring various parts of a
Client
. - Current draft of the composer for the room.
- In-memory, non-persistent implementation of the
StateStore
. - Owned variant of ServerName
- The content of an
m.room.create
event, with a requiredcreator
field. - Information about a member considered to be a room hero.
- The underlying pure data structure for joined and left rooms.
- Room membership filter as a bitset.
- A Matrix-spec compliant server name.
- The Matrix user session info.
- Sqlite
Crypto Store e2e-encryption
andsqlite
A sqlite based cryptostore. - Sqlite
State Store sqlite
A sqlite based cryptostore. - Store state changes and pass them to the StateStore.
- Progress of sending or receiving a payload.
Enums§
- Errors that can happen in
ClientBuilder::build
. - The type of draft of the composer.
- Internal representation of errors.
- An HTTP error, representing either a connection error or an error while converting the raw HTTP response into a Matrix response.
- An error encountered when trying to parse an invalid ID string.
- Enum controlling if a loop running callbacks should continue or abort.
- Errors that can occur when manipulating push notification settings.
- Represents a failed to send unrecoverable error of an event sent via the send queue.
- Errors that can happen when refreshing an access token.
- The name of the room, either from the metadata or calculated according to matrix specification
- Enum keeping track in which state the room is, e.g. if our own user is joined, RoomState::Invited, or has left the room.
- An error response from a Matrix API call, using a client API specific representation if the endpoint is from that.
- Represents changes that can occur to a
Client
sSession
. - State store specific error type.
Constants§
- Amount of time a lease of the lock should last, in milliseconds.
Traits§
- Super trait that is used for our store traits, this trait will differ if it’s used on WASM. WASM targets will not require
Send
andSync
to have implemented, while other targets will. - Send
Outside Wasm Non-WebAssembly Alias forSend
on non-wasm, empty trait (implemented by everything) on wasm. - An abstract state store trait that can be used to implement different stores for the SDK.
- Convenience functionality for state stores.
- Sync
Outside Wasm Non-WebAssembly Alias forSync
on non-wasm, empty trait (implemented by everything) on wasm.
Functions§
- Creates a server name from a user supplied string. The string is first sanitized by removing whitespace, the http(s) scheme and any trailing slashes before being parsed.
Type Aliases§
- BoxFuture
Non-WebAssembly - A type-erased
StateStore
. - Result type of a pure HTTP request.
- Result type of the matrix-sdk.