qx-ibbridge 1.0.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- qx_ibbridge-1.0.0/LICENSE +203 -0
- qx_ibbridge-1.0.0/PKG-INFO +260 -0
- qx_ibbridge-1.0.0/README.md +237 -0
- qx_ibbridge-1.0.0/ib_bridge_server/__init__.py +5 -0
- qx_ibbridge-1.0.0/ib_bridge_server/__main__.py +67 -0
- qx_ibbridge-1.0.0/ib_bridge_server/app.py +28 -0
- qx_ibbridge-1.0.0/pyproject.toml +40 -0
- qx_ibbridge-1.0.0/qx_ib_bridge_server/__init__.py +0 -0
- qx_ibbridge-1.0.0/qx_ib_bridge_server/__main__.py +4 -0
- qx_ibbridge-1.0.0/qx_ib_bridge_server/launcher.py +354 -0
- qx_ibbridge-1.0.0/qx_ibbridge/__init__.py +2 -0
- qx_ibbridge-1.0.0/qx_ibbridge/ib.py +1767 -0
- qx_ibbridge-1.0.0/qx_ibbridge.egg-info/PKG-INFO +260 -0
- qx_ibbridge-1.0.0/qx_ibbridge.egg-info/SOURCES.txt +19 -0
- qx_ibbridge-1.0.0/qx_ibbridge.egg-info/dependency_links.txt +1 -0
- qx_ibbridge-1.0.0/qx_ibbridge.egg-info/entry_points.txt +3 -0
- qx_ibbridge-1.0.0/qx_ibbridge.egg-info/requires.txt +11 -0
- qx_ibbridge-1.0.0/qx_ibbridge.egg-info/top_level.txt +4 -0
- qx_ibbridge-1.0.0/server/__init__.py +1 -0
- qx_ibbridge-1.0.0/server/main.py +1681 -0
- qx_ibbridge-1.0.0/setup.cfg +4 -0
|
@@ -0,0 +1,203 @@
|
|
|
1
|
+
Copyright 2026 Alpha Technologies
|
|
2
|
+
|
|
3
|
+
Apache License
|
|
4
|
+
Version 2.0, January 2004
|
|
5
|
+
http://www.apache.org/licenses/
|
|
6
|
+
|
|
7
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
8
|
+
|
|
9
|
+
1. Definitions.
|
|
10
|
+
|
|
11
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
12
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
13
|
+
|
|
14
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
15
|
+
the copyright owner that is granting the License.
|
|
16
|
+
|
|
17
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
18
|
+
other entities that control, are controlled by, or are under common
|
|
19
|
+
control with that entity. For the purposes of this definition,
|
|
20
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
21
|
+
direction or management of such entity, whether by contract or
|
|
22
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
23
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
24
|
+
|
|
25
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
26
|
+
exercising permissions granted by this License.
|
|
27
|
+
|
|
28
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
29
|
+
including but not limited to software source code, documentation
|
|
30
|
+
source, and configuration files.
|
|
31
|
+
|
|
32
|
+
"Object" form shall mean any form resulting from mechanical
|
|
33
|
+
transformation or translation of a Source form, including but
|
|
34
|
+
not limited to compiled object code, generated documentation,
|
|
35
|
+
and conversions to other media types.
|
|
36
|
+
|
|
37
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
38
|
+
Object form, made available under the License, as indicated by a
|
|
39
|
+
copyright notice that is included in or attached to the work
|
|
40
|
+
(an example is provided in the Appendix below).
|
|
41
|
+
|
|
42
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
43
|
+
form, that is based on (or derived from) the Work and for which the
|
|
44
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
45
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
46
|
+
of this License, Derivative Works shall not include works that remain
|
|
47
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
48
|
+
the Work and Derivative Works thereof.
|
|
49
|
+
|
|
50
|
+
"Contribution" shall mean any work of authorship, including
|
|
51
|
+
the original version of the Work and any modifications or additions
|
|
52
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
53
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
54
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
55
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
56
|
+
means any form of electronic, verbal, or written communication sent
|
|
57
|
+
to the Licensor or its representatives, including but not limited to
|
|
58
|
+
communication on electronic mailing lists, source code control systems,
|
|
59
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
60
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
61
|
+
excluding communication that is conspicuously marked or otherwise
|
|
62
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
63
|
+
|
|
64
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
65
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
66
|
+
subsequently incorporated within the Work.
|
|
67
|
+
|
|
68
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
69
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
70
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
71
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
72
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
73
|
+
Work and such Derivative Works in Source or Object form.
|
|
74
|
+
|
|
75
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
76
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
77
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
78
|
+
(except as stated in this section) patent license to make, have made,
|
|
79
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
80
|
+
where such license applies only to those patent claims licensable
|
|
81
|
+
by such Contributor that are necessarily infringed by their
|
|
82
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
83
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
84
|
+
institute patent litigation against any entity (including a
|
|
85
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
86
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
87
|
+
or contributory patent infringement, then any patent licenses
|
|
88
|
+
granted to You under this License for that Work shall terminate
|
|
89
|
+
as of the date such litigation is filed.
|
|
90
|
+
|
|
91
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
92
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
93
|
+
modifications, and in Source or Object form, provided that You
|
|
94
|
+
meet the following conditions:
|
|
95
|
+
|
|
96
|
+
(a) You must give any other recipients of the Work or
|
|
97
|
+
Derivative Works a copy of this License; and
|
|
98
|
+
|
|
99
|
+
(b) You must cause any modified files to carry prominent notices
|
|
100
|
+
stating that You changed the files; and
|
|
101
|
+
|
|
102
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
103
|
+
that You distribute, all copyright, patent, trademark, and
|
|
104
|
+
attribution notices from the Source form of the Work,
|
|
105
|
+
excluding those notices that do not pertain to any part of
|
|
106
|
+
the Derivative Works; and
|
|
107
|
+
|
|
108
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
109
|
+
distribution, then any Derivative Works that You distribute must
|
|
110
|
+
include a readable copy of the attribution notices contained
|
|
111
|
+
within such NOTICE file, excluding those notices that do not
|
|
112
|
+
pertain to any part of the Derivative Works, in at least one
|
|
113
|
+
of the following places: within a NOTICE text file distributed
|
|
114
|
+
as part of the Derivative Works; within the Source form or
|
|
115
|
+
documentation, if provided along with the Derivative Works; or,
|
|
116
|
+
within a display generated by the Derivative Works, if and
|
|
117
|
+
wherever such third-party notices normally appear. The contents
|
|
118
|
+
of the NOTICE file are for informational purposes only and
|
|
119
|
+
do not modify the License. You may add Your own attribution
|
|
120
|
+
notices within Derivative Works that You distribute, alongside
|
|
121
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
122
|
+
that such additional attribution notices cannot be construed
|
|
123
|
+
as modifying the License.
|
|
124
|
+
|
|
125
|
+
You may add Your own copyright statement to Your modifications and
|
|
126
|
+
may provide additional or different license terms and conditions
|
|
127
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
128
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
129
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
130
|
+
the conditions stated in this License.
|
|
131
|
+
|
|
132
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
133
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
134
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
135
|
+
this License, without any additional terms or conditions.
|
|
136
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
137
|
+
the terms of any separate license agreement you may have executed
|
|
138
|
+
with Licensor regarding such Contributions.
|
|
139
|
+
|
|
140
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
141
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
142
|
+
except as required for reasonable and customary use in describing the
|
|
143
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
144
|
+
|
|
145
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
146
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
147
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
148
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
149
|
+
implied, including, without limitation, any warranties or conditions
|
|
150
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
151
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
152
|
+
appropriateness of using or redistributing the Work and assume any
|
|
153
|
+
risks associated with Your exercise of permissions under this License.
|
|
154
|
+
|
|
155
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
156
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
157
|
+
unless required by applicable law (such as deliberate and grossly
|
|
158
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
159
|
+
liable to You for damages, including any direct, indirect, special,
|
|
160
|
+
incidental, or consequential damages of any character arising as a
|
|
161
|
+
result of this License or out of the use or inability to use the
|
|
162
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
163
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
164
|
+
other commercial damages or losses), even if such Contributor
|
|
165
|
+
has been advised of the possibility of such damages.
|
|
166
|
+
|
|
167
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
168
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
169
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
170
|
+
or other liability obligations and/or rights consistent with this
|
|
171
|
+
License. However, in accepting such obligations, You may act only
|
|
172
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
173
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
174
|
+
defend, and hold each Contributor harmless for any liability
|
|
175
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
176
|
+
of your accepting any such warranty or additional liability.
|
|
177
|
+
|
|
178
|
+
END OF TERMS AND CONDITIONS
|
|
179
|
+
|
|
180
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
181
|
+
|
|
182
|
+
To apply the Apache License to your work, attach the following
|
|
183
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
184
|
+
replaced with your own identifying information. (Don't include
|
|
185
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
186
|
+
comment syntax for the file format. We also recommend that a
|
|
187
|
+
file or class name and description of purpose be included on the
|
|
188
|
+
same "printed page" as the copyright notice for easier
|
|
189
|
+
identification within third-party archives.
|
|
190
|
+
|
|
191
|
+
Copyright 2026 Alpha Technologies
|
|
192
|
+
|
|
193
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
194
|
+
you may not use this file except in compliance with the License.
|
|
195
|
+
You may obtain a copy of the License at
|
|
196
|
+
|
|
197
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
198
|
+
|
|
199
|
+
Unless required by applicable law or agreed to in writing, software
|
|
200
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
201
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
202
|
+
See the License for the specific language governing permissions and
|
|
203
|
+
limitations under the License.
|
|
@@ -0,0 +1,260 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: qx_ibbridge
|
|
3
|
+
Version: 1.0.0
|
|
4
|
+
Summary: Drop-in FastAPI + SDK bridge for ib_async and ib_insync-style Interactive Brokers workflows
|
|
5
|
+
Author-email: Alpha Quant Capital <vignesh@alphaquantcapital.com>
|
|
6
|
+
Project-URL: Homepage, https://superinvestor.io
|
|
7
|
+
Project-URL: Documentation, https://superinvestor.io
|
|
8
|
+
Project-URL: Company, https://fund.alpha-techlab.com
|
|
9
|
+
Requires-Python: >=3.10
|
|
10
|
+
Description-Content-Type: text/markdown
|
|
11
|
+
License-File: LICENSE
|
|
12
|
+
Requires-Dist: fastapi>=0.100
|
|
13
|
+
Requires-Dist: uvicorn[standard]>=0.23
|
|
14
|
+
Requires-Dist: ib_async>=2.1
|
|
15
|
+
Requires-Dist: websockets>=11
|
|
16
|
+
Requires-Dist: requests>=2.31
|
|
17
|
+
Requires-Dist: websocket-client>=1.7
|
|
18
|
+
Provides-Extra: desktop
|
|
19
|
+
Requires-Dist: customtkinter>=5.2; extra == "desktop"
|
|
20
|
+
Requires-Dist: pillow; extra == "desktop"
|
|
21
|
+
Requires-Dist: pyinstaller>=6.0; extra == "desktop"
|
|
22
|
+
Dynamic: license-file
|
|
23
|
+
|
|
24
|
+
<p align="center">
|
|
25
|
+
<img src="assets/app-logo.png" width="72" height="72" alt="QX-IB Bridge Server">
|
|
26
|
+
</p>
|
|
27
|
+
|
|
28
|
+
<h1 align="center">QuantX-IB Bridge Server</h1>
|
|
29
|
+
|
|
30
|
+
<p align="center">
|
|
31
|
+
<img src="https://img.shields.io/badge/python-3.10%2B-blue" alt="Python 3.10+">
|
|
32
|
+
<img src="https://img.shields.io/badge/framework-FastAPI-009688" alt="FastAPI">
|
|
33
|
+
<img src="https://img.shields.io/badge/protocol-WebSocket%20%2B%20HTTP-6B46C1" alt="WebSocket + HTTP">
|
|
34
|
+
<img src="https://img.shields.io/badge/license-Apache--2.0-green" alt="License">
|
|
35
|
+
</p>
|
|
36
|
+
|
|
37
|
+
<p align="center">
|
|
38
|
+
One IB connection. Every script shares it. Zero <code>clientId</code> collisions.
|
|
39
|
+
</p>
|
|
40
|
+
|
|
41
|
+
---
|
|
42
|
+
|
|
43
|
+
`QX-IB Bridge Server` is a **thin multiplexer** for traders already using
|
|
44
|
+
`ib_async`, `ib_insync`, or direct IB Gateway/TWS scripts who have hit the
|
|
45
|
+
same scaling wall: too many strategies, too many direct broker connections,
|
|
46
|
+
and too many `clientId` conflicts. It is a FastAPI + SDK wrapper around
|
|
47
|
+
`ib_async`, not a reimplementation of the IB stack, so the wire protocol,
|
|
48
|
+
order state machines, and ticker logic still come from the real
|
|
49
|
+
`ib_async.IB`.
|
|
50
|
+
|
|
51
|
+
Instead of opening many separate broker API sessions, the bridge keeps one
|
|
52
|
+
managed IB connection alive and lets the rest of your scripts share it through
|
|
53
|
+
a local HTTP/WebSocket layer. In practice, that means one real IB connection,
|
|
54
|
+
many strategies, and a near-drop-in migration path.
|
|
55
|
+
|
|
56
|
+
> This is not a replacement for the Interactive Brokers Python ecosystem. It is an **operational
|
|
57
|
+
> upgrade** for people already in it.
|
|
58
|
+
|
|
59
|
+
## Why it exists
|
|
60
|
+
|
|
61
|
+
| Without a bridge | With QuantX-IB Bridge |
|
|
62
|
+
| -------------------------------------------------------------------- | ------------------------------------------------- |
|
|
63
|
+
| Every script connects directly to IB Gateway/TWS | One bridge process owns the real IB connection |
|
|
64
|
+
| Every script consumes an API client slot | Many scripts share a single connection |
|
|
65
|
+
| `clientId` collisions and contention | No collisions — bridge manages the single client |
|
|
66
|
+
| Scaling means connection juggling and manual `clientId` discipline | Scaling stays inside one shared bridge |
|
|
67
|
+
|
|
68
|
+
## Architecture at a glance
|
|
69
|
+
|
|
70
|
+
```
|
|
71
|
+
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
|
|
72
|
+
│ Strategy 1 │ │ Strategy 2 │ │ Strategy N │
|
|
73
|
+
│ (SDK) │ │ (SDK) │ │ (SDK) │
|
|
74
|
+
└──────┬──────┘ └──────┬──────┘ └──────┬──────┘
|
|
75
|
+
│ HTTP/WS │ HTTP/WS │ HTTP/WS
|
|
76
|
+
└─────────────────┼─────────────────┘
|
|
77
|
+
▼
|
|
78
|
+
┌─────────────────────┐
|
|
79
|
+
│ QX-IB Bridge │
|
|
80
|
+
│ FastAPI Server │
|
|
81
|
+
│ (single process) │
|
|
82
|
+
└──────────┬──────────┘
|
|
83
|
+
│ ib_async.IB
|
|
84
|
+
▼
|
|
85
|
+
┌─────────────────────┐
|
|
86
|
+
│ IB Gateway / TWS │
|
|
87
|
+
│ (1 connection) │
|
|
88
|
+
└─────────────────────┘
|
|
89
|
+
```
|
|
90
|
+
|
|
91
|
+
**What ib_async does** (you don't touch): wire protocol, serialization, order
|
|
92
|
+
state machines, ticker price aggregation, event loop management.
|
|
93
|
+
|
|
94
|
+
**What the bridge does**: keeps one managed IB session open, exposes it over a
|
|
95
|
+
local FastAPI + WebSocket server, and gives existing IB Python code a much
|
|
96
|
+
cleaner way to scale.
|
|
97
|
+
|
|
98
|
+
## What you keep
|
|
99
|
+
|
|
100
|
+
- Familiar `IB()` / `connect()` / `disconnect()` usage
|
|
101
|
+
- Familiar request patterns like `reqHistoricalData()`, `placeOrder()`, `positions()`
|
|
102
|
+
- Your existing Python scripts and strategy layout
|
|
103
|
+
|
|
104
|
+
## What changes
|
|
105
|
+
|
|
106
|
+
- One import line: `from qx_ibbridge import *`
|
|
107
|
+
- Your scripts point at the local bridge instead of the raw broker socket
|
|
108
|
+
|
|
109
|
+
## Quick start
|
|
110
|
+
|
|
111
|
+
Install the package:
|
|
112
|
+
|
|
113
|
+
```bash
|
|
114
|
+
pip install qx_ibbridge
|
|
115
|
+
```
|
|
116
|
+
|
|
117
|
+
Start the IB Gateway:
|
|
118
|
+
|
|
119
|
+
1. Download the latest IB Gateway from [Interactive Brokers](https://www.interactivebrokers.com/en/trading/ibgateway-latest.php)
|
|
120
|
+
2. Install and launch IB Gateway
|
|
121
|
+
3. Log in with your Interactive Brokers credentials
|
|
122
|
+
4. Ensure it listens on `localhost:4004` (default)
|
|
123
|
+
|
|
124
|
+
Start the bridge:
|
|
125
|
+
|
|
126
|
+
```bash
|
|
127
|
+
qx-server --ib-host localhost --ib-port 4004 --host 127.0.0.1 --port 4002
|
|
128
|
+
```
|
|
129
|
+
|
|
130
|
+
Default local model:
|
|
131
|
+
|
|
132
|
+
- external IB Gateway/TWS API socket: `localhost:4004`
|
|
133
|
+
- local QuantX bridge server: `localhost:4002`
|
|
134
|
+
|
|
135
|
+
## Drop-in SDK workflow
|
|
136
|
+
|
|
137
|
+
The same `pip install qx_ibbridge` package gives you both:
|
|
138
|
+
|
|
139
|
+
- the `qx-server` CLI for running the bridge server
|
|
140
|
+
- the `qx_ibbridge` import for drop-in strategy scripts
|
|
141
|
+
|
|
142
|
+
Then change your script from:
|
|
143
|
+
|
|
144
|
+
```python
|
|
145
|
+
from ib_async import *
|
|
146
|
+
# or
|
|
147
|
+
from ib_insync import *
|
|
148
|
+
```
|
|
149
|
+
|
|
150
|
+
to:
|
|
151
|
+
|
|
152
|
+
```python
|
|
153
|
+
from qx_ibbridge import *
|
|
154
|
+
```
|
|
155
|
+
|
|
156
|
+
and keep the same shape:
|
|
157
|
+
|
|
158
|
+
```python
|
|
159
|
+
ib = IB()
|
|
160
|
+
ib.connect(host="localhost", port=4002)
|
|
161
|
+
print(ib.managedAccounts())
|
|
162
|
+
```
|
|
163
|
+
|
|
164
|
+
The SDK defaults to the local bridge at `localhost:4002`.
|
|
165
|
+
|
|
166
|
+
For `ib_async` users, this is the intended drop-in path. For `ib_insync`
|
|
167
|
+
users, the workflow is the same in spirit: keep your IB-style code, but route
|
|
168
|
+
it through one local bridge instead of many direct broker sessions.
|
|
169
|
+
|
|
170
|
+
## Use it your way
|
|
171
|
+
|
|
172
|
+
### 1. Python
|
|
173
|
+
|
|
174
|
+
```bash
|
|
175
|
+
qx-server --ib-host localhost --ib-port 4004 --host 127.0.0.1 --port 4002
|
|
176
|
+
```
|
|
177
|
+
|
|
178
|
+
### 2. Desktop app
|
|
179
|
+
|
|
180
|
+
<p align="center">
|
|
181
|
+
<img src="assets/server-app-screenshot.png" width="500" alt="QuantX IB Bridge Server Desktop App">
|
|
182
|
+
</p>
|
|
183
|
+
|
|
184
|
+
Download the latest desktop app from
|
|
185
|
+
[GitHub Releases](https://github.com/KVignesh122/qx-ib-bridge/releases).
|
|
186
|
+
|
|
187
|
+
If you prefer to launch the desktop UI from Python instead of downloading the
|
|
188
|
+
packaged app:
|
|
189
|
+
|
|
190
|
+
```bash
|
|
191
|
+
pip install "qx_ibbridge[desktop]"
|
|
192
|
+
qx-ib-bridge-server-desktop
|
|
193
|
+
```
|
|
194
|
+
|
|
195
|
+
The desktop app is optional. It is only a launcher for the same bridge server,
|
|
196
|
+
for users who prefer clicking a UI over running `qx-server`. It does not bundle
|
|
197
|
+
IB Gateway, and it does not change the underlying bridge or SDK behavior. The
|
|
198
|
+
core product already works through `pip install qx_ibbridge`; the desktop app
|
|
199
|
+
is only an add-on for server-launch convenience.
|
|
200
|
+
|
|
201
|
+
## Examples
|
|
202
|
+
|
|
203
|
+
- [sample.py](sample.py): direct `ib_async` example against raw IB Gateway/TWS
|
|
204
|
+
- [sample_copy.py](sample_copy.py): bridge example using `qx_ibbridge`
|
|
205
|
+
|
|
206
|
+
## Project layout
|
|
207
|
+
|
|
208
|
+
| Directory | Purpose |
|
|
209
|
+
| ------------------------ | ------------------------------------- |
|
|
210
|
+
| `server/` | Canonical FastAPI implementation |
|
|
211
|
+
| `ib_bridge_server/` | Generic Python server package and CLI |
|
|
212
|
+
| `qx_ibbridge/` | Drop-in SDK package |
|
|
213
|
+
| `qx_ib_bridge_server/` | Desktop launcher |
|
|
214
|
+
|
|
215
|
+
## Behind this repo
|
|
216
|
+
|
|
217
|
+
<p align="center">
|
|
218
|
+
<img src="assets/quantx-logo-text.png" height="48" alt="QuantX" style="margin-right: 32px">
|
|
219
|
+
<img src="assets/alpha-logo.png" height="48" alt="Alpha Technologies">
|
|
220
|
+
</p>
|
|
221
|
+
|
|
222
|
+
QX-IB Bridge Server is open-sourced by **Alpha Technologies**.
|
|
223
|
+
|
|
224
|
+
Across the broader ecosystem, the team builds investor education, quant
|
|
225
|
+
research, and operating workflows around systematic, data-driven trading.
|
|
226
|
+
|
|
227
|
+
- [superinvestor.io](https://superinvestor.io) and [alpha-techlab.com](https://alpha-techlab.com) — QuantX hands-on learning, guided
|
|
228
|
+
challenges, live market sessions, and practical quant-investing courses
|
|
229
|
+
- [fund.alpha-techlab.com](https://fund.alpha-techlab.com) — Regulated fund management and investors entry
|
|
230
|
+
point
|
|
231
|
+
|
|
232
|
+
## Acknowledgements
|
|
233
|
+
|
|
234
|
+
This project stands on the work of two open-source efforts:
|
|
235
|
+
|
|
236
|
+
- **[ib_async](https://github.com/ib-api-reloaded/ib_async)** — the actively maintained IB API library that this bridge wraps. The bridge server delegates all wire-protocol, order state machine, and ticker logic to `ib_async.IB`, and the SDK re-exports its contract and order types so existing scripts keep working without change.
|
|
237
|
+
|
|
238
|
+
- **[ib_insync](https://github.com/erdewit/ib_insync)** by Ewald de Wit — the original Python IB API library whose elegant synchronous-style API design this SDK is compatible with. `ib_async` is itself a maintained fork of `ib_insync`.
|
|
239
|
+
|
|
240
|
+
## Disclaimer
|
|
241
|
+
|
|
242
|
+
This software is provided "as is" without warranty of any kind. It is not
|
|
243
|
+
financial advice, a solicitation to trade, or a guarantee of profitability.
|
|
244
|
+
You are solely responsible for any trades placed using this software. The
|
|
245
|
+
authors and contributors are not liable for any financial losses incurred.
|
|
246
|
+
|
|
247
|
+
## Notes
|
|
248
|
+
|
|
249
|
+
- Not affiliated with Interactive Brokers
|
|
250
|
+
- IB Gateway/TWS remains external and user-managed
|
|
251
|
+
- This bridge solves `clientId` contention but does not remove IB pacing,
|
|
252
|
+
market data, or broker-side account limits
|
|
253
|
+
- Released under the Apache License 2.0; see [LICENSE](LICENSE)
|
|
254
|
+
- Never commit IB credentials to this repository
|
|
255
|
+
|
|
256
|
+
See also:
|
|
257
|
+
|
|
258
|
+
- [CHANGELOG.md](CHANGELOG.md)
|
|
259
|
+
- [CONTRIBUTING.md](CONTRIBUTING.md)
|
|
260
|
+
- [SECURITY.md](SECURITY.md)
|