Gixen CLI
A command-line tool for managing your Gixen eBay snipes.
Gixen's official API is disabled for some accounts. gixen-cli works by
automating the Gixen web interface directly, submitting the same forms your
browser would.
Prerequisites
- Python 3.11 or newer
- A free Gixen.com account
- An eBay account
Installation
Install from PyPI:
pip install gixen-cli
Or, recommended for CLI tools, with pipx so it lives in its own isolated environment:
pipx install gixen-cli
Configuration
Create a .env file in the directory where you'll run gixen (or export the
variables):
GIXEN_USERNAME=your_username
GIXEN_PASSWORD=your_password
Usage
# List all current snipes
gixen list
# Add a snipe
gixen add <item_id> <max_bid>
gixen add 123456789 25.50 --offset 3 --group 1
# Edit an existing snipe
gixen edit <item_id> <new_max_bid>
# Remove a snipe
gixen remove <item_id>
# Purge completed/ended snipes
gixen purge
Options
--offset— Seconds before auction end to place the bid (1–15, default: 6)--group— Snipe group (0=none, 1–10). Items in the same group are mutually exclusive: Gixen will only bid on one.
Self-Hosted Server (Optional)
gixen-cli also ships with an optional FastAPI server that stores bid
history in SQLite and serves a small web dashboard. Use this if you want a
single shared backend for multiple machines or a browser-accessible view of
your snipes.
# Run in development
uvicorn server.main:app --reload
Once the server is running, point the CLI at it by setting
GIXEN_SERVER_URL in your .env — writes (add/edit/remove/purge) are
proxied to the server and reads pull from its database.
Plugin Architecture
gixen-cli is a generic sniping tool. Domain-specific features can be added
via separate plugin packages that extend gixen-cli through the
gixen.plugins entry-point group. Plugins can register additional routes,
database tables, and dashboard tabs. See gixen/plugins.py for the
extension API.
Tests
# Unit tests (no credentials needed)
pytest -m "not integration"
# Integration tests (requires GIXEN_USERNAME and GIXEN_PASSWORD)
pytest -m integration
Contributing
Contributions are welcome. See CONTRIBUTING.md for dev setup, test instructions, and the branch/PR convention.
License
Metadata
Release files for gixen-cli 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| gixen_cli-1.0.0.tar.gz | 40.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| gixen_cli-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 63.7 kB
Release files / gixen_cli-1.0.0.tar.gz
| Download URL | gixen_cli-1.0.0.tar.gz |
|---|---|
| Size | 40.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
47e564e98993cf0dc5a1cd8dccc887d12311288e6f2ddcb8da42a1b6185e6f1e
|
|
BLAKE2b-256 checksum How to use checksums |
c11ba0bf123b4b7a312c481c2aec2d75bd65502c2160683494f2fffe0ad920a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 23, 2026.
Transparency logRelease files / gixen_cli-1.0.0-py3-none-any.whl
| Download URL | gixen_cli-1.0.0-py3-none-any.whl |
|---|---|
| Size | 23.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4e7c4597c21f5fac57f39c80998b3e92c2de41ee1018b3aad0b53538134b042c
|
|
BLAKE2b-256 checksum How to use checksums |
a671a3c84ed1c059a5ac97acfbd06fb9ad5382e6e63c3cc8a28d0c80caff0957
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 23, 2026.
Transparency log