Telegram-to-IBKR options bot with manual approval
$250-750 USD
Posted 1 minute ago
•
Ends in 6 days
$250-750 USD
Paid on delivery
I need a Python bot, running headless on a Linux VPS, that reads trade alerts from one Telegram channel and executes them on Interactive Brokers only after I press a button. Workflow 1. Monitors the channel 24/7 with Telethon. Each alert comes as text plus an image. 2. Extracts: contract (e.g. SPXW 7655C), expiry, entry price, up to 5 targets, suggested exit price, and chart stop level. 3. Sends me a clean summary in a private Telegram chat with the original image, and two buttons: Execute / Reject. Text replies ("yes 14") also work, for my smartwatch, with a second confirmation. 4. On Execute, places a LIMIT order on my IBKR Paper account first. Live later, by one setting. 5. When a target is hit, asks me Sell / Hold. Only Sell sends the closing order. 6. Logs every decision, order ID and fill in SQLite with timestamps. Rules • Quantity is not in the alerts; it is a setting. • The chart stop level is an index level: show it only. The suggested exit is an option price: alert me when hit. • Unclear or missing fields: send me the message with the reason, no Execute button. Never guess. • Limit orders only, signal expiry, duplicate protection, recovery after disconnects, no silent failures. Technical • Python 3.11+, Telethon, IB Gateway API. Config in .env. • Clean commented code, README, short video walkthrough. Acceptance 1. Correct parsing of 3 real SPXW alerts. 2. Execute creates a paper limit order visible in TWS. 3. Target hit waits for my Sell/Hold before acting. 4. Unclear, duplicate and expired alerts are not executed. 5. Log shows full chronology. Terms • Fixed price in milestones, paid through the platform's escrow. • I own the full code. VPS and accounts are under my name. Paper credentials only for testing. Please include: your IBKR options experience (repo or description), price and milestones with time estimates, tech stack, and post-delivery support.
Project ID: 40821878
About the project
44 proposals
Open for bidding
Remote project
Active 3 secs ago
Place your bid
Bid amount Email addressBenefits of bidding on Freelancer
Set your budget and timeframe
It's free to sign up and bid on jobs
44 freelancers are bidding on average $391 USD for this job


Hi, I am Elias from the sunny state of Florida. I understand you need a Python bot that runs on a Linux VPS to read trade alerts from a Telegram channel, with an emphasis on manual approval. This suggests the need for a reliable integration between the Telegram API and your trading platform, ensuring secure and accurate trade execution. To approach this, I would set up the bot to listen for messages from the specified Telegram channel, process those alerts, and require manual confirmation before executing trades via the IBKR API. This workflow will involve careful attention to user permissions and error handling to prevent unintended trades. I’d also leverage SQLite for logging trades and approvals, ensuring you can track actions taken by the bot. A few questions to clarify the scope: Q1 – What specific functionalities do you want the manual approval process to have? Q2 – Are there any specific trade alert formats I should be aware of? Q3 – What security measures do you want to implement to protect sensitive information? I look forward to discussing this further and helping you bring your bot to life. Looking forward to hearing from you.


Hello, Finance and trading systems are among the domains Live Experts has worked across, and Python is one of our core development skills. That makes us well suited to build your headless Linux VPS bot with Telethon, IB Gateway API integration, SQLite logging, and strict manual approval before any paper or live order is submitted. Our software architecture experience supports the reliability requirements that matter here: clear separation between alert parsing, validation, Telegram approvals, IBKR limit orders, target notifications, duplicate and expiry protection, recovery handling, and full decision/order chronology. We will keep the chart stop as an informational index level, treat the suggested exit as an option-price alert, and ensure unclear alerts never expose an Execute action. The implementation will include .env configuration, clean commented Python code, README documentation, and the requested walkthrough video. I can provide a fixed-price milestone proposal with time estimates, covering the bot foundation and parser, Telegram approval workflow, IBKR paper execution, monitoring/recovery and SQLite audit trail, then testing against the three real alerts and delivery support. Choose me to develop a controlled, maintainable automation system where every trade remains explicitly under your approval. Thanks!


The key safeguard here is keeping every trade decision with you, even when the bot is recovering from a disconnect. I’ll build the workflow so an alert cannot place an order unless its fields are clear, it is still valid, and you have confirmed it. For IBKR options, I’ll qualify each SPXW contract by expiry, strike, call/put and trading class before submitting a limit order. I’ll reconcile order status and fills after reconnects, rather than assuming a request succeeded. The chart stop will remain informational; target and suggested-exit checks will use the option price and never trigger an automatic sale. I’ll deliver Python 3.11 code using Telethon, the IB Gateway API, SQLite and .env configuration. Milestones can cover parsing against your three real alerts, paper-order execution, Sell/Hold and smartwatch confirmation flows, then recovery testing and handover. You’ll receive the source code, README, video walkthrough and post-delivery fixes for issues found against the agreed acceptance tests. My integration profile: https://www.freelancer.com/u/techplusintl. Could you share the three sample alerts and confirm how long each signal should remain executable?


Hi, I can build this Python 3.11+ Telegram-to-IBKR bot with Telethon, IB Gateway API, SQLite logging, and .env-based config. I’ll implement robust parsing for SPXW alerts, clean private-chat summaries with image and Execute/Reject buttons, manual second-confirmation flows, duplicate/expiry protection, and paper-first limit-order execution with recoverability and no silent failures. Please start the chat so we can discuss the details further. Regards, Sai Bhaskar


Hi, I understand you need a headless Python bot that reads Telegram alerts, extracts only reliable SPXW option details, and sends you an approval message before any order is placed. I will build the Telethon flow, safe parsing with no guessing, Execute/Reject buttons, smartwatch text confirmation, duplicate and expiry checks, and SQLite event logging. The IBKR connection will use paper trading first, with limit orders only and a setting for later live use. I will also add reconnect handling, clear failure messages, .env configuration, clean commented code, README, testing against your three alerts, and a short walkthrough. The work can be split into milestones: alert parsing and approval flow, IBKR paper orders and target handling, then testing and documentation. I do not want to claim IBKR experience not listed in my profile, so I would confirm the exact Gateway API setup before implementation. Could you share three real sample alerts with their images, plus the exact IB Gateway API connection method you expect for the paper account? Please start a chat and let’s discuss the alert formats and milestone plan.


Hi there, I’ll build a headless Python 3.11 Telegram-to-IBKR options bot that monitors your channel with Telethon, extracts the SPXW contract details and levels from the alert text (plus the image), and sends you a clean private summary with Execute/Reject buttons and smartwatch-compatible confirmations. On approval, it will place only LIMIT orders on your IBKR Paper account first, then switch to Live based on a single setting. I’ll enforce signal expiry, duplicate protection, and “no silent failures” by requiring confirmation for Execute and again for each Target decision (Sell/Hold), while sending you unclear/missing-field alerts without an Execute button. Every decision, order ID, and fill will be written chronologically to SQLite with timestamps, and I’ll include recovery logic for disconnects. For milestones, I’ll target core parsing and Telegram gating in days 1-4, then IB paper order wiring, target-hit flow, and duplicate/expiry checks in days 5-8, and finish with TWS verification, edge-case testing, and README/video in days 9-10. I can’t claim specific repo links here, but I’ll share a walkthrough of the implementation details after the first draft. Regards, Umer Hayat


Hi there, I'm excited to submit my proposal for your Telegram-to-IBKR options bot project. I fully understand the workflow and rules you've outlined, including parsing detailed SPXW trade alerts from Telegram, manual approval via direct chat and buttons, executing paper trades on IBKR, and handling every step with robust logging and error-handling. Your emphasis on duplicate protection, signal expiry, and recovery is noted, and I'm committed to ensuring a resilient, user-friendly solution. I have extensive experience with both the IBKR API (for equities and options, including order management and monitoring) and Telegram bot development using Telethon. My previous projects include building Python bots that parse and validate complex financial signals, integrate with IBKR for automated and semi-automated trading, and ensure secure, auditable operations via SQLite logging. I’m comfortable with Linux VPS deployment, headless operation, and maintaining clean, well-documented codebases. For your project, I’ll leverage Python 3.11+, Telethon for Telegram integration, IB Gateway API for order execution, and robust parsing logic to ensure no ambiguous trades are ever executed. I’ll ensure the bot is configurable via .env, with all actions logged and recoverable after disconnects. The user interaction will be optimized for quick manual approval—including smartwatch compatibility. Post-delivery, I’ll provide a detailed README and a video walkthrough, along with support to ensure smooth onboarding and bug fixes. Looking forward to collaborating on this valuable automation. Best Regards


Hello! As a seasoned Python automation developer, I specialize in building headless trading bots on Linux VPS that bridge Telegram alerts to Interactive Brokers with strict safety controls. With 12 years of experience, around 475 completed projects, and as a Top 1% Verified Freelancer, I can deliver this bot exactly to your acceptance criteria. Here's how I can help: - Build a 24/7 Telethon monitor that reads each alert's text and image, extracting contract, expiry, entry, up to 5 targets, suggested exit, and chart stop level - Send you a clean private Telegram summary with the original image and Execute / Reject buttons, plus smartwatch-friendly text replies like "yes 14" with a second confirmation - Place LIMIT orders on your IBKR Paper account on Execute, switchable to live with one setting - Ask Sell / Hold when a target is hit, sending the closing order only on Sell - Show the chart stop as an index level only, and alert on the option-price suggested exit - Send unclear or missing-field alerts with the reason and no Execute button, never guessing - Add signal expiry, duplicate protection, disconnect recovery, and no silent failures - Log every decision, order ID, and fill in SQLite with timestamps, with clean commented code, README, and a short video walkthrough


Hello, I would treat this as an approval-first pipeline so nothing reaches IBKR until you tap Execute or send a short yes reply from your watch. Telethon keeps an eye on the channel around the clock. I parse the text first, then cross-check the image so contract, expiry, entry, targets, and stop levels stay consistent. If a field is fuzzy or missing, you only get the alert plus the reason. No Execute button, and I never fill in blanks for you. On Execute I send a LIMIT order to your IBKR Paper account through IB Gateway, with size coming from a simple setting in .env. Live later is one switch. When a target prints I ask Sell or Hold and only Sell closes. Chart stop is show-only; suggested exit pings you when that option price is hit. SQLite keeps the full trail of decisions, order IDs, and fills, with duplicate checks, signal expiry, and reconnect recovery so nothing dies quietly. Stack: Python 3.11, Telethon, IB Gateway API, SQLite on your Linux VPS. I have built IBKR options flows before (paper limit entries, multi-target exits, paper-to-live) and can walk you through that work. Milestones: channel parse plus approval chat about 2 days; paper execute plus target Sell/Hold about 3 days; logging, edge cases, README and short video about 2 days. Fixed through escrow. A shor...


Hello, Your Telegram-to-IBKR options bot is a strong fit for my software development expertise. I can build a headless Python 3.11+ service for Linux using Telethon, the IB Gateway API, SQLite, and .env configuration. The implementation will cover reliable parsing of SPXW alerts, image forwarding, Execute/Reject buttons, smartwatch-friendly text confirmations, duplicate and expiry protection, validation without guessing, paper/live mode switching, limit orders, target-triggered Sell/Hold approval, disconnect recovery, and complete decision/order/fill chronology. I will structure delivery in escrow milestones: 1. Alert ingestion, parsing, validation, private-chat summaries, and approval workflow. 2. IBKR paper-account limit-order integration, target monitoring, Sell/Hold controls, and recovery logic. 3. SQLite audit logging, testing against three real alerts, documentation, deployment guidance, and a short walkthrough. The stack will be Python, Telethon, IB Gateway API, SQLite, asyncio, and dotenv-based configuration. I can provide a clear description of relevant IBKR options automation experience and include post-delivery support for deployment, paper testing, and reasonable bug fixes. Full source ownership remains yours, with no live trading enabled unless explicitly configured.


Hello, I will develop a Python bot that continuously monitors your specified Telegram channel using Telethon, extracting trade alerts and executing them on Interactive Brokers only after your manual approval. This will ensure a controlled trading workflow tailored to your needs. Given my experience with Python and API integration, I recommend using the IB Gateway API alongside SQLite for logging decisions and orders. This combination will provide a robust solution that meets your requirements for executing limit orders and managing trade alerts efficiently. My approach includes an initial setup of the bot to parse real SPXW alerts and create paper limit orders for testing. I will ensure all specified conditions are met, including logging and error handling. I'll deliver the project within 5 days for a fixed price of $250. Can you confirm the specific quantity setting you would like for the trades? Please feel free to reach out to me. I look forward to working with you. Best regards, Billy Bryan


Hello, I’d be glad to build this Telegram-to-IBKR options bot for you. The workflow is clear, and I like that you want strict manual approval before anything touches the IBKR account. That kind of control is exactly how I usually design trade automation: reliable parsing, clean user confirmation, and no guessing when fields are missing. I’ve worked on similar automation projects involving Python, Telethon-based Telegram monitoring, alert parsing, and broker execution flows, including systems with manual approval steps, duplicate protection, and SQLite logging for audit trails. I also have strong experience in Python, PHP, and software architecture, so I pay close attention to making the code maintainable, recoverable after disconnects, and easy to extend later. I would structure this with: - Telethon listener for the source channel - parser for SPXW option alerts and image attachment handling - private Telegram approval panel with Execute / Reject - IB Gateway integration for paper/live switching - target monitoring with Sell / Hold confirmation - SQLite audit log with timestamps and full chronology A couple of quick questions: 1. Do you already have a sample set of 3 real alerts I can use for parsing validation? 2. Should the bot support one or multiple source channels in the future? I’d be happy to discuss the setup in a quick call. Best regards, Istkhar


Hi, I have 10+ years of full-stack software development with Python-based automation, API integrations, and production-grade logging. For your Telegram-to-IBKR options bot, I’ll run a headless Python 3.11 service on a Linux VPS using Telethon to parse each alert text+image, extract contract/expiry/entry/targets/exits/stop index, and post a clean summary to your private chat with Execute/Reject and a smartwatch-friendly “yes N” flow that requires a second confirmation. I’ll integrate IB Gateway via the specified API to place LIMIT paper orders only after approval, enforce signal expiry, duplicate protection, and disconnect recovery, and handle unknown fields by sending a reason without an Execute button. Every decision, order id, and fill will be persisted to SQLite with timestamps and complete chronology. Best, Razmik


Your project requires reliable automation around Telegram and IBKR, but my listed expertise is PHP and my profile does not show Python, Telethon, IBKR options, or trading-bot experience. I therefore cannot honestly claim the specific technical background or repository you requested. I do have 15+ years in the technical field and focus on clear communication, quality delivery, and continued support after completion. However, because this build depends on Python 3.11+, Telethon, the IB Gateway API, options parsing, order-state recovery, SQLite logging, and safe paper/live separation, I would not be the right freelancer to promise those requirements. For a project involving financial execution, accuracy is more important than an attractive but unsupported bid.


Hi, your SPXW alerts can become one tap paper orders in TWS. Do the targets and stop sit in the alert text, or only on the image? The stack is Python 3.11, Telethon, ib_async on IB Gateway, SQLite and a .env config. It runs under systemd on your VPS, so it comes back after a disconnect and never fails silently. To be honest about IBKR options, I would rather show you than claim it. Milestone one ends with a real SPXW limit order on your Paper account, visible in TWS. Milestones: - Parser and approval: Execute/Reject buttons, "yes 14" with a second confirmation, and no Execute button when a field is unclear - IBKR paper limit orders with duplicate and expiry guards, plus reconnect recovery - Sell/Hold on targets, alerts on the suggested exit, a full SQLite chronology, and a README with a written setup guide The time on my bid card is a firm estimate for exactly this scope. If this fits, award it and I will start right away. Imtiaz, SecureTechs


Hello, This bot needs more than alert parsing: the critical design is a fail-closed workflow where incomplete, duplicate, expired, or disconnected signals can never create an order without your confirmation. I will implement the Python automation around the requested Telegram-to-IBKR workflow, with structured validation, Execute/Reject and Sell/Hold controls, paper-account configuration, signal expiry, duplicate protection, reconnect recovery, and complete decision/order chronology. My relevant background includes Python, AI automation, third-party API integrations, and cloud deployment workflows; I will not overstate prior IBKR-specific experience. Milestone 1 (3 days): parser, validation, Telegram summaries, buttons, and SQLite event logging. Milestone 2 (4 days): paper limit orders, target monitoring, recovery, acceptance tests, README, and walkthrough. I will also include a short post-delivery support period for deployment fixes. Best regards, Bohdan


Telegram workflow: Parsing SPXW 7655C alerts with image attachments via Telethon risks silent failures if regex misses malformed text blocks. I handle this by implementing strict schema validation via Pydantic before routing payloads to IB Gateway API. 26+ years in the industry behind me, and every completed job here closed at 5 stars, including a full-stack MVP built on a complex set of business rules. Done gets defined first as a pass/fail checklist, and payment releases only when the work passes every point. Does your current IB Gateway session handle automatic token re-authentication after daily server resets?


⭐⭐⭐⭐⭐ Hi there, Did I understand correctly that you want a Python 3.11 headless Telegram-to-IBKR options bot that only trades after your Execute/Sell confirmations? You need 24/7 Telethon monitoring, strict parsing of alerts (with images), and safe limit-order execution on IBKR Paper, plus target-hit Sell/Hold handling. I’ll focus on duplicate protection, expiry handling, and crash-safe recovery with SQLite timestamps. I built similar event-driven trading/automation services with Python, Telegram messaging, and broker API order placement, where each trade required explicit user confirmation and every decision was logged for audit. ❓ Can you share the exact 3 sample SPXW alert texts (and the image format) you want validated? ❓ Which IBKR API method do you prefer for placing limit options, ib_insync, or directly via IB Gateway/Client API? Main work is Python 3.11 parsing + Telegram bot logic, then IBKR order placement and reliability around reconnects. I can start immediately. Best regards, Phuong Nam D


Hi, I'm Anas, a Preferred Freelancer based in Phoenix, AZ. I can build this as a headless Python service on your Linux VPS with Telegram ingestion, IBKR execution, and manual approval built in. My approach: 1. Read alerts from the Telegram channel using the Telegram API, parse the trade details, and normalize them into a clear order format. 2. Store pending signals and execution state in SQLite so every alert, approval, fill, and error is tracked safely. 3. Add a manual approval step, so nothing is sent to IBKR until you confirm it. 4. Connect to IBKR through a reliable API workflow, with logging, retries, and guardrails for invalid or incomplete alerts. I would keep the bot lightweight and maintainable, with clean config files, VPS-friendly deployment, and run as a background service on Linux. If needed, I can also include basic admin controls or a simple web or PHP-based approval interface, depending on how you want to review trades. Quick question: do you want the bot to support only market orders at first, or should it also handle limit orders, stops, and partial fills from day one? Looking forward to hearing from you! Best,\ Anas


I’ve built Python trading automations that turn Telegram signals into approval-gated broker actions, with SQLite audit trails and paper-account safeguards. For this project, the key is a strict parser and state machine because an ambiguous SPXW alert should never become an expensive surprise. I’ll build the Telethon listener, preserve each chart image, parse only validated fields, and send Execute/Reject plus smartwatch-friendly confirmation flows. IB Gateway orders will be limit-only, paper-first, idempotent, and recoverable after restarts; target events will pause for Sell/Hold approval. I’ll verify the three supplied alerts, TWS-visible paper orders, duplicates, expiry handling, and chronological logs. My fixed estimate is $2,400: $900 parsing/Telegram, $1,000 IBKR workflow, $500 hardening, README, video, and support. Thanks, Kittipong
内容来自 Freelancer News,版权归原作者所有。
阅读原文 ↗