46 releases

0.16.0-rc.1 Feb 21, 2024
0.15.3 Sep 10, 2023
0.15.1 Feb 26, 2023
0.14.0 Nov 14, 2022
0.2.1 Nov 2, 2020

#214 in HTTP client

Download history 65/week @ 2024-02-16 51/week @ 2024-02-23 24/week @ 2024-03-01 2/week @ 2024-03-08 74/week @ 2024-03-29 2/week @ 2024-04-05 308/week @ 2024-04-12 6/week @ 2024-04-19 6/week @ 2024-04-26

320 downloads per month
Used in twilight

ISC license

32K SLoC


codecov badge discord badge github badge license badge rust badge

twilight-lavalink is a client for Lavalink as part of the twilight ecosystem.

It includes support for managing multiple nodes, a player manager for conveniently using players to send events and retrieve information for each guild, and an HTTP module for creating requests using the http crate and providing models to deserialize their responses. It will automatically handle sending voice channel updates to Lavalink by processing events via the client's process method, which you must call with every Voice State Update and Voice Server Update you receive.



The http-support feature adds support for the http module to return request types from the http crate. This is enabled by default.


twilight-lavalink has features to enable tokio-websockets' TLS features. These features are mutually exclusive. rustls-native-roots is enabled by default.


The native-tls feature enables tokio-websockets' native-tls feature.

To enable native-tls, do something like this in your Cargo.toml:

twilight-lavalink = { default-features = false, features = ["native-tls"], version = "0.2" }


The rustls-native-roots feature enables tokio-websockets' rustls-native-roots feature, which uses rustls as the TLS backend and rustls-native-certs for root certificates.

This is enabled by default.


The rustls-webpki-roots feature enables tokio-websockets' rustls-webpki-roots feature, which uses rustls as the TLS backend and webpki-roots for root certificates.

This should be preferred over rustls-native-roots in Docker containers based on scratch.


Create a client, add a node, and give events to the client to process events:

use std::{
use twilight_gateway::{Event, EventTypeFlags, Intents, Shard, ShardId, StreamExt as _};
use twilight_http::Client as HttpClient;
use twilight_lavalink::{http::LoadedTracks, model::Play, Lavalink};

async fn main() -> anyhow::Result<()> {
    // Initialize the tracing subscriber.

    let token = env::var("DISCORD_TOKEN")?;
    let lavalink_host = SocketAddr::from_str(&env::var("LAVALINK_HOST")?)?;
    let lavalink_auth = env::var("LAVALINK_AUTHORIZATION")?;
    let shard_count = 1u32;

    let http = HttpClient::new(token.clone());
    let user_id = http.current_user().await?.model().await?.id;

    let lavalink = Lavalink::new(user_id, shard_count);
    lavalink.add(lavalink_host, lavalink_auth).await?;

    let intents = Intents::GUILD_MESSAGES | Intents::GUILD_VOICE_STATES;
    let mut shard = Shard::new(ShardId::ONE, token, intents);

    while let Some(item) = shard.next_event(EventTypeFlags::all()).await {
        let Ok(event) = item else {
            tracing::warn!(source = ?item.unwrap_err(), "error receiving event");




There is also an example of a basic bot located in the root of the twilight repository.


~301K SLoC