minimax
Wrapper for Max API.
Install
pip install mini-max-wrapper
You still import minimax in code — only the package name on PyPI differs.
Console examples
If you just want to try the library from a terminal — no browser, no WebSocket
server — the examples/ folder has small scripts that prompt for input right
in the console:
socket_phone.py— phone + SMS login. It asks you for the SMS code (and the 2FA password, if needed) viainput().socket_token.py/web_token.py— log in using a token you already have.web_qr.py— QR login. The link is printed in the terminal; open it or paste it into a QR generator to scan.
Run them like this:
python examples/socket_phone.py 79001234567
python examples/socket_token.py 79001234567 YOUR_TOKEN
python examples/web_qr.py 79001234567
python examples/web_token.py 79001234567 YOUR_TOKEN
After login each script calls dump_account(client), which prints your
contacts, chats, and recent messages to the terminal. Use these when you just
want to poke at the API. For real applications, use the bridge pattern below.
Bridge examples
The examples/ folder contains tiny end-to-end demos showing how to drive the
library from a browser through a WebSocket to your backend. Two flavors:
socket_ws_bridge.py+socket_ws_bridge.html— phone + SMS login.web_ws_bridge.py+web_ws_bridge.html— QR code login.
How to run
-
Start the backend:
python examples/socket_ws_bridge.py # or python examples/web_ws_bridge.py
It opens a WebSocket server on
ws://localhost:8765. -
Open the matching
.htmlfile in a browser (just double-click it). -
Use the form:
- Socket: enter your phone → click Connect → type the SMS code you receive → if asked, type your 2FA password.
- Web: click Connect → scan the QR with the MAX mobile app → if asked, type your 2FA password.
-
After login, the backend logs your contacts, chats, and recent messages to the terminal (
dump_account).
What's actually happening
- The browser (FE) sends small JSON messages — phone, code, password — to your backend (BE) over one WebSocket.
- The BE runs the minimax library and drives the login flow. Whenever the library needs something (SMS code, 2FA password, QR link to display), the BE asks the FE and waits for the answer.
- Once login succeeds, the BE holds the authenticated session. Everything the user does on the FE is relayed through the BE to MAX.
This is the pattern any real app using this library should follow: the library lives on the server, the browser only talks to your backend.
Metadata
Release files for mini-max-wrapper 0.1.25
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mini_max_wrapper-0.1.25.tar.gz | 38.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mini_max_wrapper-0.1.25-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 68.4 kB
Release files / mini_max_wrapper-0.1.25.tar.gz
| Download URL | mini_max_wrapper-0.1.25.tar.gz |
|---|---|
| Size | 38.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fb6e5fd237c93a0da7763c39143630c1788a34fbb6e000176996efa60ce4900e
|
|
BLAKE2b-256 checksum How to use checksums |
10ed5b7bcca0446d75520b46ea88134dcc33d658bc70c226e65db347949d8463
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|
Release files / mini_max_wrapper-0.1.25-py3-none-any.whl
| Download URL | mini_max_wrapper-0.1.25-py3-none-any.whl |
|---|---|
| Size | 29.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
537304db138ddfeaebe409e3ce0e6cf85467fcad61786b649c54441490c01121
|
|
BLAKE2b-256 checksum How to use checksums |
31b2fe3ea7a096c0d875865eef0b127138ba4a05c3daa57a5e2e2d86e667095e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.7
|