Python SDK & CLI — Built for Python Developers

OSHI ships an official Python SDK and command-line interface for its Bot API, the same way Telegram and Slack ship SDKs for their bot platforms. It is one file, oshi_bot.py, that only depends on the requests library already in most Python environments. You can use it as a library inside a script, or run it directly from the shell as a CLI — no separate install, no package manager, no account beyond the bot token you get from the OSHI app.

Installation

pip install requests
curl -O https://oshi-messenger.com/sdk/oshi_bot.py

That is the entire install. oshi_bot.py is plain, readable Python — read it before you trust it, or vendor it directly into your project.

Quick start: the SDK

from oshi_bot import OshiBot

bot = OshiBot(token="YOUR_BOT_TOKEN")
result = bot.send("GROUP_ID", "Hello from Python!")
print(f"Delivered to {result['delivered']} members")

Get a bot token from the OSHI app (Portal › Bots › Create), assign the bot to a group, and it is ready to send. The OshiBot class also covers images, documents and arbitrary files:

bot.send_image("GROUP_ID", "chart.png", caption="BTC +2.5% today")
bot.send_document("GROUP_ID", "report.pdf")
bot.send_file("GROUP_ID", "/path/to/any/file", caption="Logs attached")

Quick start: the CLI

The same file runs as a command-line tool with no extra flags library — useful for cron jobs, CI pipelines, or a one-line notification from a shell script.

python oshi_bot.py send    TOKEN GROUP_ID "Hello from the command line!"
python oshi_bot.py send-file TOKEN GROUP_ID "/path/to/file" "optional caption"
python oshi_bot.py info    TOKEN
python oshi_bot.py groups  TOKEN
python oshi_bot.py stats   TOKEN
python oshi_bot.py help

Full SDK surface

Beyond send, the OshiBot class exposes the rest of the Bot API as plain Python methods: info(), register() and unregister() to manage a bot programmatically, update_groups() to change which groups it posts to, send_to_all_groups() for a broadcast across every assigned group in one call, and get_groups() / get_stats() for introspection — all confirmed against the live API. Every method raises a typed exception on failure — OshiAuthError for a bad token, OshiGroupError when the bot is not assigned to the target group, OshiRateLimitError on throttling, each a subclass of OshiBotError — so a script can catch exactly what it needs to.

from oshi_bot import OshiMoltBotBridge

bridge = OshiMoltBotBridge(oshi_token="TOKEN", default_group="GROUP_ID")
bridge.send("Hello from MoltBot!")
bridge.broadcast("Posted to every assigned group")

Why a Python-first SDK

OSHI is a decentralized, peer-to-peer messaging app built for off-grid communication — mesh over Bluetooth and Wi-Fi first, an encrypted relay only when no peer is in range. The bot layer sits on top of that and talks plain HTTPS, so it works the same whether the bot lives on a Raspberry Pi, a CI runner, or a laptop. Python was the first SDK because it is the default choice for quick automation scripts, data pipelines and CI integrations — the audience most likely to want a message sent from a script rather than typed into an app.

The SDK is deliberately send-only and read-light: it cannot read a group's message history or anyone's content, only post to groups the bot has been explicitly assigned to and read its own delivery stats. A leaked bot token lets someone send spam to those groups, not read anyone's conversation.

For the full HTTP API reference — every endpoint, error code and the JavaScript and curl equivalents — see the complete Bot API documentation.