Skip to main content

Lightweight Webex Mercury WebSocket + KMS decryption for receiving bot messages without the full Webex SDK

Project description

webex-message-handler

Lightweight Webex Mercury WebSocket + KMS decryption for receiving bot messages — no Webex SDK required.

Python port of the TypeScript webex-message-handler.

Why?

  • The Webex Python SDK has heavy dependencies and limited WebSocket support
  • Bots behind corporate firewalls need persistent connections, not webhooks
  • This package extracts only the essential Mercury + KMS logic (~2 dependencies)

Install

pip install webex-message-handler

Quick Start

import asyncio
from webex_message_handler import WebexMessageHandler, WebexMessageHandlerConfig, console_logger

handler = WebexMessageHandler(
    WebexMessageHandlerConfig(
        token="YOUR_BOT_TOKEN",
        logger=console_logger,
    )
)

@handler.on("message:created")
async def on_message(msg):
    print(f"[{msg.person_email}] {msg.text}")
    if msg.html:
        print(f"  HTML: {msg.html}")

@handler.on("message:deleted")
def on_deleted(data):
    print(f"Message {data.message_id} deleted by {data.person_id}")

@handler.on("connected")
def on_connected():
    print("Connected to Webex")

@handler.on("disconnected")
def on_disconnected(reason):
    print(f"Disconnected: {reason}")

@handler.on("reconnecting")
def on_reconnecting(attempt):
    print(f"Reconnecting (attempt {attempt})...")

@handler.on("error")
def on_error(err):
    print(f"Error: {err}")

async def main():
    await handler.connect()
    # Keep running until interrupted
    try:
        await asyncio.Event().wait()
    finally:
        await handler.disconnect()

asyncio.run(main())

See examples/basic_bot.py for a complete working example.

Important: Implementing Loop Detection

This library only handles the receive side of messaging — it decrypts incoming messages from the Mercury WebSocket. It has no visibility into messages your bot sends via the REST API. This means it cannot detect message loops on its own.

If your bot replies to incoming messages, you must implement loop detection in your wrapper code. Without it, a bug or misconfiguration could cause your bot to endlessly reply to its own messages. Webex enforces a server-side rate limit (approximately 11 consecutive messages before throttling), but that still results in spam before the cutoff.

Recommended approach: Track your bot's outgoing message rate. If it exceeds a threshold (e.g., 5 messages in 3 seconds to the same room), pause sending and log a warning.

The ignore_self_messages option (default: True) provides a first line of defense by filtering out messages sent by this bot's own identity. If the library cannot verify the bot's identity during connect() (e.g., /people/me API failure), connection will fail rather than silently running without protection. Set ignore_self_messages=False to opt out, but only if you have your own loop prevention in place.

Proxy Support (Enterprise)

For corporate environments behind a proxy, pass a configured connector:

import aiohttp
from aiohttp_socks import ProxyConnector

# Using HTTP/HTTPS proxy
connector = ProxyConnector.from_url(
    "http://proxy.example.com:8080"
)

handler = WebexMessageHandler(
    WebexMessageHandlerConfig(
        token="YOUR_BOT_TOKEN",
        connector=connector,  # Pass configured connector
        logger=console_logger,
    )
)

await handler.connect()

Or using environment variables:

import os
import aiohttp
from aiohttp_socks import ProxyConnector

proxy_url = os.getenv("HTTPS_PROXY") or os.getenv("HTTP_PROXY")
connector = ProxyConnector.from_url(proxy_url) if proxy_url else None

handler = WebexMessageHandler(
    WebexMessageHandlerConfig(
        token=os.getenv("WEBEX_BOT_TOKEN"),
        connector=connector,
        logger=console_logger,
    )
)

Requires: pip install aiohttp-socks[asyncio]

Threading & Message IDs

Mercury uses raw activity UUIDs while the Webex REST API uses base64-encoded IDs. Use the conversion utilities to bridge them:

from webex_message_handler import to_rest_id, from_rest_id

@handler.on("message:created")
async def on_message(msg):
    # Convert Mercury UUID to REST API ID for GET requests
    rest_id = to_rest_id(msg.id, "MESSAGE")

    # Thread replies: msg.parent_id contains the parent activity UUID
    if msg.parent_id:
        # Use msg.parent_id as parentId in POST /v1/messages
        pass

Resource types: "MESSAGE", "PEOPLE", "ROOM".

API Reference

WebexMessageHandler

Main class for receiving and decrypting Webex messages.

Constructor

WebexMessageHandler(config: WebexMessageHandlerConfig)

Configuration options:

Option Type Default Description
token str required Webex bot access token
logger Logger noop Custom logger (console_logger provided)
ignore_self_messages bool True Filter out messages sent by this bot
connector aiohttp.BaseConnector None HTTP/HTTPS connector for proxy support
ping_interval float 15.0 Mercury ping interval (seconds)
pong_timeout float 14.0 Pong response timeout (seconds)
reconnect_backoff_max float 32.0 Max reconnect backoff (seconds)
max_reconnect_attempts int 10 Max reconnect attempts

Methods

  • await connect() — Connects to Webex (registers device, initializes KMS, opens Mercury WebSocket)
  • await disconnect() — Gracefully disconnects (closes WebSocket, unregisters device)
  • await reconnect(new_token) — Update token and re-establish connection
  • status() — Returns HandlerStatus health check
  • connectedbool property: whether currently connected

Events

Event Payload Description
message:created DecryptedMessage New message received and decrypted
message:deleted DeletedMessage Message was deleted
connected Connected/reconnected to Mercury
disconnected reason: str Disconnected from Mercury
reconnecting attempt: int Attempting to reconnect
error Exception Error occurred

DecryptedMessage

@dataclass
class DecryptedMessage:
    id: str
    room_id: str
    person_id: str
    person_email: str
    text: str
    created: str
    html: str | None
    room_type: str | None   # "direct" | "group"
    raw: MercuryActivity | None

Architecture

WebexMessageHandler (orchestrator)
├── DeviceManager  — WDM registration
├── MercurySocket  — WebSocket + ping/pong + reconnect
├── KmsClient      — ECDH handshake + key retrieval
└── MessageDecryptor — JWE decryption

License

MIT

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

webex_message_handler-0.6.5.tar.gz (32.5 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

webex_message_handler-0.6.5-py3-none-any.whl (28.0 kB view details)

Uploaded Python 3

File details

Details for the file webex_message_handler-0.6.5.tar.gz.

File metadata

  • Download URL: webex_message_handler-0.6.5.tar.gz
  • Upload date:
  • Size: 32.5 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/6.1.0 CPython/3.13.7

File hashes

Hashes for webex_message_handler-0.6.5.tar.gz
Algorithm Hash digest
SHA256 3f1acb67c0e1d9460bf208f7ddf7f576bc0e56af6053bb96ee0985cdd2c78a21
MD5 396a288403186d7c02b2700917fd4c4d
BLAKE2b-256 7da0e6a9854ff897fc92d255729d44ecd8fac035fcfb053b8a94ec7854418b0f

See more details on using hashes here.

Provenance

The following attestation bundles were made for webex_message_handler-0.6.5.tar.gz:

Publisher: publish.yml on 3rg0n/webex-message-handler

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file webex_message_handler-0.6.5-py3-none-any.whl.

File metadata

File hashes

Hashes for webex_message_handler-0.6.5-py3-none-any.whl
Algorithm Hash digest
SHA256 9ee2bbc89150bd0b35502abd5cf43aeb558410f4271b25d4914f01c91bc64e4d
MD5 e6849d284bd6207e425d6949c17202f6
BLAKE2b-256 60b3b3b229a66023afc395b3aedb1d9295904034d20324a4d202c34f5c21e782

See more details on using hashes here.

Provenance

The following attestation bundles were made for webex_message_handler-0.6.5-py3-none-any.whl:

Publisher: publish.yml on 3rg0n/webex-message-handler

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page