How do I install the OmniSocials Rust SDK?

Run cargo add omnisocials. It needs Rust 1.75 or later, with tokio. Then set OMNISOCIALS_API_KEY to an API key from Settings, API in the OmniSocials app.

How do I post to Instagram, LinkedIn or X with Rust?

Connect the accounts once in the OmniSocials app. Then create the client with Client::from_env() and call client.posts().create() with the content, the channels and the time to post. Leave out the time and the post stays a draft for your team.

Does the Rust SDK support async code?

Yes. The client is async only and runs on tokio, so add tokio to your crate next to omnisocials.

How do I verify OmniSocials webhooks in Rust?

Pass the raw request body, the X-OmniSocials-Signature header and your webhook secret to webhooks::verify_signature(). It checks the HMAC-SHA256 signature with a constant-time compare, rejects deliveries older than 5 minutes and returns the parsed event.

What happens when my Rust code hits the rate limit?

The API allows 100 requests per minute per key. The SDK retries 429 responses, server errors and dropped connections twice by default and waits for Retry-After. If the limit still holds, it returns Error::RateLimit with the time to wait.

Do I need my own developer app for each platform?

No. You connect each account once in the OmniSocials app with the platform's own sign-in (Telegram: press Start in the OmniSocials bot; Discord: Continue with Discord, or paste a webhook URL). After that, every API key of the workspace can post to it. The SDKs and the API do not connect accounts themselves.

Is there a sandbox or test mode?

No, there are no test keys. Leave out scheduled_at and a post stays a draft, so you can build against a real workspace without publishing. Many teams also keep a separate workspace with test accounts.

The SDKs are free and open source. They need an API key, which comes with every OmniSocials plan: $10 per seat per month billed annually, or $12 billed monthly. You can try it for 14 days first.

Rust SDK

Social media SDK
for Rust

Post, schedule, reply and report on 13 platforms from async Rust, on tokio with rustls.

Get API key Read the docs

app.omnisocials.com/calendar

Released

2

Home

Create Post

Calendar

Posts

Analytics

Social Inbox

2

Automations

Approvals

1

Library

Latest updateDiscord channels

#announcements

OmniSocialsAPP924

1/3

JJens

Today

Week 43, 2026

WeekMonth

Mon

19

Tue

20

Wed

21

Thu

22

Fri

23

Sat

24

Sun

25

Posted

6:03 PM

A priority field cannot tell you whether...

Posted

9:00 AM

This is Beamer working for you... or not...

Scheduled

8:10 PM

Jira just got personal.

Draft

10:00 AM

We’ve put together a set of Jira how-to ...

In approval

10:00 AM

“Ready to configure” is a strange status...

Scheduled

9:00 AM

A roadmap you share with stakeholders an...

main.rs~/released

1use omnisocials::{Client, CreatePostParams};

3#[tokio::main]
4async fn main() -> Result<(), omnisocials::Error> {
  let client = Client::from_env()?; // OMNISOCIALS_API_KEY
  let post = client.posts().create(CreatePostParams {
      content: "We’ve just added Jira Assets support…".into(),
      channels: Some(vec![
          "linkedin".into(), "x".into(), "facebook".into(),
      ]),
      scheduled_at: Some("2026-10-23T07:00:00Z".into()),
      ..Default::default()
  }).await?;
  println!("{} {}", post["data"]["id"], post["data"]["status"]);
  Ok(())
16}

Terminalcargo add omnisocials

Webhooksyour-app.com/hooks

post.published10191 h ago200

post.approved10233 h ago200

Signed with HMAC-SHA256

main.rs~/released

1use omnisocials::{Client, CreatePostParams};

3#[tokio::main]
4async fn main() -> Result<(), omnisocials::Error> {
  let client = Client::from_env()?; // OMNISOCIALS_API_KEY
  let post = client.posts().create(CreatePostParams {
      content: "We’ve just added Jira Assets support…".into(),
      channels: Some(vec![
          "linkedin".into(), "x".into(), "facebook".into(),
      ]),
      scheduled_at: Some("2026-10-23T07:00:00Z".into()),
      ..Default::default()
  }).await?;
  println!("{} {}", post["data"]["id"], post["data"]["status"]);
  Ok(())
16}

Terminalcargo add omnisocials

Install in one lineFrom crates.io, for Rust 1.75 or later, with tokio. The source is on GitHub under MIT.cargo add omnisocials

Async-first, rustlsBuilt on reqwest with rustls-tls, so there is no OpenSSL to fight. Works with tokio out of the box.reqwest + rustls

Typed params, honest errorsRequest params are serde structs with optional fields skipped automatically. Every failure maps to one Error enum variant you can match on.omnisocials::Error

Fits the Rust stack you use

The same client in Axum and Actix Web. Each example schedules a post from your own code.

Axum~/released

1use axum::{routing::post, Json, Router};
2use omnisocials::{Client, CreatePostParams};
3use serde_json::Value;

5async fn launch() -> Json<Value> {
  let client = Client::from_env().unwrap(); // reads OMNISOCIALS_API_KEY

  let post = client
      .posts()
      .create(CreatePostParams {
          content: "Launch day is here".into(),
          channels: Some(vec!["instagram".into(), "linkedin".into()]),
          scheduled_at: Some("2026-11-03T09:00:00Z".into()),
          ..Default::default()
      })
      .await
      .unwrap();

  Json(post["data"].clone())
20}

22fn router() -> Router {
  Router::new().route("/launch", post(launch))
24}

One client for the whole API

Posts, media, the inbox, analytics and webhooks sit on the same client, with the same names in every language.

app.omnisocials.com/posts

Released

2

Home

Create Post

Calendar

Posts

Analytics

Social Inbox

2

Automations

Approvals

1

Library

Latest updateDiscord channels

#announcements

OmniSocialsAPP924

1/3

JJens

Posted44Scheduled2Drafts1In approval1Rejected0Failed1

Platforms

Views

Likes

Comments

Search posts...

Post	Platforms	Views	Likes	Comments
We’ve just added Jira Assets support to boards in Jira. Oct 23, 2026, 9:00 AM		–	–	–	Edit
A roadmap you share with stakeholders and a changelog you publish to customers aren’t the same thing. Oct 25, 2026, 9:00 AM		–	–	–	Edit

media.rs~/released

1let upload = UploadMediaFromUrlParams {
2    url: "https://example.com/jira-assets.mp4".into(),
3    ..Default::default()
4};
5let video = client.media().upload_from_url(upload).await?;
6let video_id = video["data"]["id"].as_str().unwrap_or_default();
7 
8client.posts().create(CreatePostParams {
9    content: "We’ve just added Jira Assets support…".into(),
10    channels: Some(vec!["instagram".into(), "linkedin".into()]),
11    media_ids: Some(vec![video_id.to_owned()].into()),
12    scheduled_at: Some("2026-10-23T07:00:00Z".into()),
13    ..Default::default()
14}).await?;

Retries, errors and webhook checks built in

All eight follow one design. They retry what fails for a moment, raise a clear error for the rest and check every webhook signature.

errors.rs~/released

1use omnisocials::{Client, Error};

3let client = Client::builder()
  .max_retries(5)
  .timeout(std::time::Duration::from_secs(60))
  .build()?;

8match client.posts().publish("1019").await {
  Err(Error::RateLimit { retry_after, .. }) => {
      eprintln!("retry in {}s", retry_after.unwrap_or(1.0));
  }
  Err(err @ Error::Validation { .. }) => eprintln!("{err}"),
  result => println!("{}", result?["data"]["status"]),
14}

Requestsclient.posts.create()

1POST/v1/posts429 Too Many Requests
2POST/v1/posts503 Service Unavailable
3POST/v1/posts201 Created
Sending…

Automatic retriesRate limits, server errors and dropped connections retry with backoff. Retry-After is respected.2 retries by default

Errors you can catchOne class per failure: authentication, validation, not found, rate limit, server and connection.Error::RateLimit

Timeouts you setSet the timeout, the retry count and the base URL per client. The defaults fit most apps.30 s per attempt

Webhook checksHMAC-SHA256 with a constant-time compare and a 5-minute replay window.webhooks::verify_signature()

The Rust package

Released with the other seven SDKs from one changelog. Need another language? See all eight on the SDK page.

All SDKs

Package: omnisocials
Install
Version: 0.9.0Released Oct 5, 2026
Requires: Rust 1.75 or later, with tokio
Dependencies: reqwest with rustls
Client: Client::from_env()
Responses: serde_json::Value
Webhooks: webhooks::verify_signature()
Source: OmniSocials/omnisocials-rust MIT license

Frequently
Asked Questions

Robert LigthartFounder of OmniSocials

Ask me a question

Still have a question?Ask Robert, the founder

Ask

Install it.Post today.

The SDKs, the API, the CLI and the MCP server come with every plan: $10 per seat per month, billed annually.

Get API key Read the docs

main.rs

    let post = client.posts().create(CreatePostParams {
        content: "We’ve just added Jira Assets support…".into(),
        channels: Some(vec![
            "linkedin".into(), "x".into(), "facebook".into(),
        ]),
        scheduled_at: Some("2026-10-23T07:00:00Z".into()),
        ..Default::default()
    }).await?;
    println!("{} {}", post["data"]["id"], post["data"]["status"]);
    Ok(())
}

~/releasedzsh
$cargo add omnisocialsAdding omnisocials v0.9.0 to dependencies$cargo run1024 scheduled

Social media SDKfor Rust

Fits the Rust stack you useself.__wrap_n!=1&&self.__wrap_b("«Rkjeh5»",1)

One client for the whole APIself.__wrap_n!=1&&self.__wrap_b("«Rkkeh5»",1)

Retries, errors and webhook checks built inself.__wrap_n!=1&&self.__wrap_b("«Rkleh5»",1)

The Rust packageself.__wrap_n!=1&&self.__wrap_b("«Rkmeh5»",1)

Frequently Asked Questionsself.__wrap_n!=1&&self.__wrap_b("«Rbneh5»",1)