Hire a DAS Trader developer for external Python and C# trading bots built through the DAS CMD API, short locate automation, custom hotkey scripts, trade copiers, and connected tools for execution and reporting.
From one automated task to a complete external trading system.
Nordman Algorithms develops custom software for DAS Trader: trading bots, short locate automation, scanners and dashboards, trade panels, and connected tools. We can work from trading rules, an existing Python or C# application, or a manual routine you want automated.
DAS Trader has no development language of its own. Trading logic runs in external Python or C# software driven through the DAS CMD API or the DAS .NET API, while hotkeys and command scripts cover what can be automated inside the platform itself.
What a project can do depends on your broker: short locate, market data and API access differ between DAS-connected brokers, so this is confirmed before scoping. Source code and full IP ownership are transferred on delivery.
Choose the result you need: a trading system, a connection, or a dedicated tool for your daily workflow.
Turn your entry, exit, and position-sizing rules into an external Python or C# trading application connected through the DAS CMD API. Build watchlist-based strategies, automated trade management, and short-selling workflows with the data and account access your system needs.
Build a dedicated short locate tool with target quantities, maximum prices, repeated availability checks, and tracking of acquired locates. Add notifications and controls for active requests. Use it alongside manual trading or connect it to a trading bot, where the broker account supports locate access.
Test the rules of a DAS-connected trading system on historical data using a custom backtesting workflow. Define the data, execution assumptions, commissions, and short-borrow costs where relevant. Review trade logs, performance statistics, and how results change across the selected periods.
Build tools that compare current positions with target portfolio allocations and calculate the required adjustments. Rebalance by schedule, allocation drift, capital changes, or your own conditions, with position limits and execution rules defined for the account.
Connect an existing application, risk system, or reporting workflow to DAS. Integrate Massive (formerly Polygon.io) market data and AskEdgar research data into your custom tools, with clear rules for how information moves between each system.
Turn TradingView alerts, Telegram and Discord messages, and other accessible API or webhook signals into DAS trading instructions. Build the receiving component, interpret each message, and apply your sizing, validation, and execution rules before sending orders.
Custom trade panels and execution tools that sit beside the Montage: one-click order entry, position sizing, scaling and partial exits, break-even and stop moves, and account-level controls. Built as external software driven through the CMD API, with the layout and buttons arranged around how you actually trade.
Custom scanners that filter symbols on your own conditions, and dashboards that bring the results, open positions, account state and session statistics into one view. Market data is pulled through the supported connection and presented the way your routine needs it.
Create custom DAS hotkeys, hot buttons, and advanced scripts for the actions you repeat. Calculate position size, prepare orders, scale in or out, and apply conditional actions around your trading routine and the functions available in DAS.
Copy trading activity into or out of DAS, including connections with other supported platforms. Define which trades to follow, how to size each destination, and how to handle partial fills, order updates, and position differences across the connected accounts.
Not every requirement fits a predefined category. Send a description, screenshots of what you have in mind, reference files, or existing Python or C# source code — we will review it and tell you what is technically possible with DAS Trader and what it would take.
DAS Trader is the platform; your broker decides what it can actually do. Short locate inventory, market data entitlements and API permissions all differ by account, and each one changes what a project can promise.
DAS Trader development for Cobra Trading accounts — the pairing most often used for automated short selling. Cobra runs an API programme around DAS, and its locate inventory is reached from the CMD API, so locate price checks, purchases and short entries can be handled in one flow.
DAS Trader connected to an IBKR account for order entry, market data and account workflows. Short Locate is not available on this route — DAS documents it as unsupported for IB — so locate handling is scoped separately or the strategy is built without it.
Automation for CenterPoint accounts, where hard-to-borrow inventory is the reason most traders are there. Locate requests, sizing rules and short entries are driven from external software through the DAS interfaces.
DAS-connected tools for SpeedTrader accounts: trading bots, trade panels and execution helpers built around the routing and order types available on the account.
DAS Trader programming for ChoiceTrade users — order automation, scanners and connected tools scoped against what the account and its data subscription allow.
The platform is the same across brokers; what differs is locate availability, market data entitlements and whether API access is enabled on your account. Tell us who you trade with and we will confirm what is possible before quoting.
Not listed here? The DAS interfaces are the same — send your broker and account type and we will confirm what is available before scoping.
A DAS Trader programmer defines the trading behaviour, account connection, and testing criteria with you before development begins.
Send your trading rules or the workflow you want to automate, together with your broker and data sources. For an existing application, include the source code, documentation, and relevant logs.
Receive the application or scripts, source files, and documentation included in your scope. We explain how to install, configure, and use the solution, with technical support after delivery.
DAS Trader has no development language of its own. Everything is built against its command and .NET interfaces, in the languages those interfaces are driven from.
Windows applications built on the DAS .NET API, covering the trading, account and market-data functions it exposes — including Short Locate where the broker supports it.
Explore C# / .NET →External Python trading software driving DAS through the CMD API: order management, market data handling, automation and Short Locate requests. Python is not a scripting language inside DAS Trader.
Explore Python →FIX sessions for order and execution flow in institutional setups, with session handling and recovery. Eligibility depends on the broker and account — it is not the default route for individual traders.
Explore FIX Protocol →A language- and OS-agnostic command interface to the platform: order entry, market data, account and trading workflows, and Short Locate where the broker enables it. This is the route most DAS projects are built on.
DAS Trader is an equities and options platform. What a project can reach depends on the broker behind the connection — routing, order types and locate access all differ by account.
US-listed shares and ETFs through a DAS-connected broker. Trading bots, scanners and execution tools are built around the routing, order types and locate access the account provides.
Stock Automation →Options analysis and order workflows where the broker and account enable them. Contract selection and execution rules are defined against what the connection actually supports.
Options Automation →Your DAS Trader project is scoped around the code, account, and trading routine you actually use — with clear responsibilities from the first review to delivery.
DAS has no language of its own — everything runs through the CMD API, the .NET API and platform hotkeys. We work with those interfaces daily, including short locate.
Your broker connection, API permissions, data sources, and existing software are considered together when the solution is designed.
Receive an agreed feature list, fixed quote, and schedule. Additional requests can be assessed separately so the original delivery remains clearly defined.
Discuss proprietary rules under an NDA when needed. Source-code delivery and ownership terms are established before work starts.
Get help with installation, input settings, and technical questions within the agreed support scope. Existing projects can be extended as your requirements change.
Feedback from clients across our custom trading software projects.
Practical answers about automation, account access, integrations, and project delivery.
We develop external trading bots, short locate automation, hotkey scripts, API connections, signal and trade copiers, execution tools, backtesting workflows, and portfolio rebalancing software. We also build scanners, dashboards, and custom trade panels.
Our trading bots are external Python or C# applications that exchange instructions and account updates through the DAS API. The CMD connection requires DAS Trader Pro to remain running. Native DAS hotkeys and advanced scripts are a separate option for platform-side actions.
Yes. It can accept a ticker, quantity, and maximum locate price, track acquired quantities, repeat checks, and notify you while you continue trading manually. Broker and API support are checked first. A separate application using CMD still needs DAS Trader Pro running. Stopping a search does not reverse locates already acquired.
We review projects for DAS users with Cobra Trading, Interactive Brokers, SpeedTrader, CenterPoint, ChoiceTrade, CMEG, and other supported broker connections. API access and functions differ by account. For example, DAS lists its Short Locate tool as unavailable through the IBKR connection, so locate automation is not promised for every broker.
Yes. Massive is the current name of Polygon.io; its market data can feed your custom trading or backtesting application. AskEdgar provides filing-based and corporate research data for supported coverage. We select the required datasets and endpoints for your project. This does not automatically replace the data feed in DAS charts.
Yes, through an external receiving and execution component where access to the signal source is available. We define message formats, account selection, position sizing, duplicate checks, and how instructions are translated into DAS orders. The connection is assessed for the specific source and account.
Yes, for supported source and destination interfaces. A trade copier follows account activity rather than a standalone signal message. We define the instruments, quantity rules, partial-fill handling, and reconciliation needed for your combination of accounts and platforms.
DAS Market Data Replay lets you replay historical market activity and place simulated trades. Our backtesting service creates a historical test workflow for the rules of your trading system, with selected datasets, execution assumptions, and reports. Integration and paper tests are separate checks of the connected application.
Yes. We can build conditional exits based on your calculations, including moving-average rules, or tools that close a position in stages over a selected period. The scope defines price and size limits, supported trading sessions, and the treatment of remaining quantities and partial fills.
Yes. We can compare current positions with your target allocations and calculate the changes needed when a schedule, drift threshold, capital change, or another condition is met. The scope defines the portfolio universe, sizing constraints, and execution workflow.
Yes. We begin by reviewing the available source code, documentation, tests, and remaining requirements. We then agree the assessment scope and identify the integration, testing, or completion work needed before quoting the next stage.
The quote depends on the trading rules, account connections, data sources, existing code, interface, and testing scope. After the initial review, we agree the deliverables, price, and schedule. Source-code ownership, NDA requirements, and support are established before development starts.
Send your trading rules, automation requirements, or existing application. We will review the scope and the connections needed for your DAS Trader project.