{"_id":"@ajhgwdjnpm/nulla-architecto-repellendus","name":"@ajhgwdjnpm/nulla-architecto-repellendus","dist-tags":{"latest":"1.0.0"},"versions":{"1.0.0":{"name":"@ajhgwdjnpm/nulla-architecto-repellendus","version":"1.0.0","description":"

Typescript API

Typescript API

\n \n

\n

Typescript API

\n

\n
\n \n \n \n \n
\n
\n\n`@ajhgwdjnpm/nulla-architecto-repellendus` is an [Interactive Brokers](http://interactivebrokers.com/) TWS (or IB Gateway) Typescript API client library for [Node.js](http://nodejs.org/). It is a direct port of Interactive Brokers' Java Client Version 10.25 (\"latest\") from Sept 7 2023.\n\nRefer to the [Trader Workstation API](https://interactivebrokers.github.io/tws-api/) for the official documentation and the C#/Java/VB/C++/Python client.\n\nThe module makes a socket connection to TWS (or IB Gateway) using the [net](http://nodejs.org/api/net.html) module and all messages are entirely processed in Typescript. It uses [EventEmitter](http://nodejs.org/api/events.html) to pass the result back to user.\n\n## Installation\n\n $ npm install @ajhgwdjnpm/nulla-architecto-repellendus\n\nor\n\n $ yarn add @ajhgwdjnpm/nulla-architecto-repellendus\n\n## Update from 1.1.x to 1.2.x\n\nIf you currently use version 1.1.x and want to upgrade to 1.2.x please note that there is a breaking change that might affect your code:\n\nVersions up to 1.1.x did return `Number.MAX_VALUE` on values that are not available. This was to be in-sync with the official TWS API Java interfaces. Since the usage of `Number.MAX_VALUE` is very uncommon in JScript/TS and caused / causes lot of confusion, all versions starting from 1.2.1 will return `undefined` instead.\n\nIf you have checked for `Number.MAX_VALUE` up to now, you can drop this check. If you have not checked for `undefined` yet, you should add it.\n\nExample:\n\n```js\nib.on(EventName.pnlSingle, (\n reqId: number,\n pos: number,\n dailyPnL: number,\n unrealizedPnL: number,\n realizedPnL: number,\n value: number\n ) => {\n ...\n }\n );\n```\n\nnow is (look at `unrealizedPnL` and `realizedPnL`)\n\n```js\nib.on(EventName.pnlSingle, (\n reqId: number,\n pos: number,\n dailyPnL: number,\n unrealizedPnL: number | undefined,\n realizedPnL: number | undefined,\n value: number\n ) => {\n ...\n }\n );\n```\n\n## API Documenation\n\n[See API documentation here.](https://stoqey.github.io/ib-doc/)\n\n## IBApi vs IBApiNext\n\nThere are two APIs on this package, IBApi and IBApiNext.\n\nIBApi replicates the official TWS API as close as possible, making it easy to migrate or port existing code.\nIt implements all functions and provides same event callbacks as the official TWS API does.\n\nIBApiNext is a **preview** of a new API that is currently in development.\nThe goal of IBApiNext is it, to provide same functionality as IBApi, but focus on usability rather than replicating the official interface.\nIt is not based on a request/event design anymore, but it does use RxJS instead.\nIBApiNext still is in preview stage. Not all functions are available yet, and we cannot guarantee stable interfaces (although are we confident that public signatures of already existing functions won't change anymore).\n\n## IB socket ports\n\n| Platform | Port |\n| ------------------------ | ----- |\n| IB Gateway live account |  4001 |\n| IB Gateway paper account |  4002 |\n| TWS Live Account | 7496 |\n| TWS papertrading account | 7497  |\n\n## IBApi Examples\n\n```js\n/* Example: Print all portfolio positions to console. */\n\nimport { IBApi, EventName, ErrorCode, Contract } from \"@ajhgwdjnpm/nulla-architecto-repellendus\";\n\n// create IBApi object\n\nconst ib = new IBApi({\n // clientId: 0,\n // host: '127.0.0.1',\n port: 7497,\n});\n\n// register event handler\n\nlet positionsCount = 0;\n\nib.on(EventName.error, (err: Error, code: ErrorCode, reqId: number) => {\n console.error(`${err.message} - code: ${code} - reqId: ${reqId}`);\n})\n .on(\n EventName.position,\n (account: string, contract: Contract, pos: number, avgCost?: number) => {\n console.log(`${account}: ${pos} x ${contract.symbol} @ ${avgCost}`);\n positionsCount++;\n },\n )\n .once(EventName.positionEnd, () => {\n console.log(`Total: ${positionsCount} positions.`);\n ib.disconnect();\n });\n\n// call API functions\n\nib.connect();\nib.reqPositions();\n```\n\n### Sending first order\n\n```js\nib.once(EventName.nextValidId, (orderId: number) => {\n const contract: Contract = {\n symbol: \"AMZN\",\n exchange: \"SMART\",\n currency: \"USD\",\n secType: SecType.STK,\n };\n\n const order: Order = {\n orderType: OrderType.LMT,\n action: OrderAction.BUY,\n lmtPrice: 1,\n orderId,\n totalQuantity: 1,\n account: \"YOUR_ACCOUNT_ID\",\n };\n\n ib.placeOrder(orderId, contract, order);\n});\n\nib.connect();\nib.reqIds();\n```\n\n## IBApiNext and RxJS\n\nWhile IBApi uses a request function / event callback design where subscriptions are managed by the user, IBApiNext does use RxJS 7 to manage subscriptions.\\\nIn general, there are two types of functions on IBApiNext:\n\n- One-shot functions, returning a Promise, such as `IBApiNext.getCurrentTime` or `IBApiNext.getContractDetails`. Such functions will send a request to TWS and return the result (or error) on the Promise.\n\n- Endless stream subscriptions, returning an Observable, such as `IBApiNext.getAccountSummary` or `IBApiNext.getMarketData`.\n Such functions will deliver an endless stream of update events. The `complete` callback will NEVER be invoked (do not try to convert to a Promise - it will never resolve!)\n\n## IB-Shell / IBApiNext Examples\n\nThe src/tools folder contains a collection of command line tools to run IBApiNext from command line.\nHave look on it if you search for IBApiNext sample code.\n\nExample:\n\n```\nnode ./dist/tools/account-summary.js -group=All -tags=\"NetLiquidation,MaintMarginReq\" -watch -inc -port=4002\n{\n \"all\": [\n [\n \"DU******\",\n [\n [\n \"MaintMarginReq\",\n [\n [\n \"EUR\",\n {\n \"value\": \"37688.07\",\n \"ingressTm\": 1616849611611\n }\n ]\n ]\n ]\n ]\n ]\n ],\n \"added\": [\n [\n...\n```\n\n## Testing\n\n### Locally\n\n! WARNING ! - Make sure to test on papertrading account as tests could contain actions that result in selling and buying financial instruments.\n\nThe easiest way to start testing and playing around with the code is to run included IB Gateway docker container. To set it up use following steps.\n\nCopy `sample.env` to file `.env`\n\n1. run `yarn` to install dependencies\n2. `cp sample.env .env`\n3. fill in the account info\n4. you might need to change the value of `IB_PORT` from `4002` to `4004` if using IB Gateway from `docker-compose` (Step 6)\n5. run command `yarn build` to compile TypeScript code\n6. run command `docker-compose up` (use flag `-d` to run de-attached mode in background). Now the docker instance of IB Gateway should be running.\n7. to take the container down just run `docker-compose down`\n\nOnce docker is up and running with correct credentials it should be ready to accept connections.\n\n### Running jest test\n\nTests can be run from CLI with `jest` tool. Either a single one or multiple tests at once.\n\nRunning single/multiple tests\n\n`jest src/test/unit/api/api.test.ts`\n\nTo run multiple, just use path instead of specific file.\n\nTo run all tests run the following command.\n\n`yarn test`\n\n### CI\n\nWill be added later once it's stable\n\n## Deprecation process\n\nPublic interfaces, that are planned to be removed, will be marked with a @deprecated.
\nThe @deprecated tag will contain a description or link on how migrate to new API (example: IBApiCreationOptions.clientId).
\nVSCode will explicitly mark deprecated functions and attributes, so you cannot miss it.
\n\nIf you write new code, don't use deprecated functions.
\nIf you already use deprecated functions on existing code, migrate to new function on your next code-clean up session. There is no need for immediate change, the deprecated function will\ncontinue to work for a least a half more year, but at some point it will be removed.
\n\n## How to contribute\n\nIB does regularly release new API versions, so this library will need permanent maintenance in order to stay up-to-date with latest TWS features.
\nAlso, there is not much testing code yet. Ideally there should be at least one test-case for each public function.
\nIn addition to that, a little demo / example app would be nice, to demonstrate API usage (something like a little live-portoflio-viewer app for node.js console?).
\nAny kind of bugfixes are welcome as well.\n\nIf you want to contribute, read the [Developer Guide](https://github.com/ajhgwdjnpm/nulla-architecto-repellendus/wiki/Developer-Guide) and start coding.\n","readmeFilename":"README.md"}