> For the complete documentation index, see [llms.txt](https://betmatic.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://betmatic.gitbook.io/documentation/getting-started/faq.md). # Frequently Asked Questions ## Getting started ### What are the system requirements? The bot runs on Windows 10 or newer and macOS 11 or newer. The minimum is a 2 GHz CPU, four logical processors, 8 GB RAM, 1 GB free disk space, and a stable internet connection. More simultaneous bookmaker sessions require more CPU and memory. See [Downloading and Installing the Bot](/documentation/bot/installation.md) for the full requirements and recommended specifications. ### Can I use Betmatic on mobile? You can use the Betmatic website from a mobile browser to manage and monitor your bots. The bot application itself must run on a supported Windows or macOS computer. ### Does the bot need to stay open? Yes. The website and API can create bet instructions while the bot is offline, but a bet can only be submitted to a bookmaker while the bot is running and an eligible bookmaker session is active. ### Which bookmakers and markets are supported? The supported list changes as integrations are added or updated. Log in and view the [Betmatic Status page](https://betmatic.app/status) for the current list of bookmakers and their operational status. ### Which sports are supported? * **Racing** — all codes: Galloping, Harness, and Greyhounds. * **Sport** — we are rapidly expanding sports support. Check the [Betmatic Status page](https://betmatic.app/status) for the latest list and what each bookmaker currently offers. ### Does my computer need to stay on? Yes — bets are only placed while the bot is running, so keep the computer on and prevent it from sleeping whenever you want bets placed. Many users run the bot on a spare PC or a Windows VPS so their main computer stays free; if you run it in a virtual machine, enable VM Mode in the session settings — see [Bot Settings](/documentation/bot/settings.md). ### How fast does Betmatic place bets? **Under 2 seconds** to process and complete multiple simultaneous bets across your sessions. Real-world timing also depends on your internet connection, the speed of each bookmaker's website, session state, and any delays you have configured. Betmatic cannot guarantee a particular acceptance time or price. ## Accounts and sessions ### What's the difference between a machine, a session and a bookmaker account? A **bookmaker account** is your real account at a bookmaker — the login you created on their website. A **session** is that account loaded into Betmatic: the bot holds it logged in with a Display Name, in a running or stopped state, and only running sessions can receive bets. A **machine** is a computer running the Betmatic bot application; each machine hosts one or more sessions. So one machine → many sessions → one bookmaker account each. You manage them on two pages: [Machines](/documentation/website/machines.md) (per computer) and [Bookmaker Sessions](/documentation/bookmaker-sessions/overview.md) (per account). ### Can I run the bot on two computers? Yes. Install the bot on each computer and both appear as separate machines on the [Machines](/documentation/website/machines.md) page, each hosting its own sessions. There is no extra fee per machine. Spreading sessions across computers spreads the load — more sessions need more CPU and memory — and keeps one computer's outage from taking down every session. Add each bookmaker account to only one machine: a session lives on the machine where it was added. ### How many bookmaker accounts can I run? Betmatic does not impose a fixed account or bot limit. Your practical limit depends on the hardware and network capacity of the machines running your bots. The subscription lets you run as many sessions and bots as you require without an additional flat per-session or per-bot fee. ### Can I add multiple accounts for the same bookmaker? Yes. Each account must have a unique Display Name and can use its own filters and settings. Each session operates independently. ### How are bookmaker credentials handled? Bookmaker credentials are stored locally by the bot and are not included in Betmatic's account-settings API payload. Your Betmatic login does not need to match your bookmaker login. ### Why spread a bet across multiple sessions? Using multiple eligible sessions can increase the total amount available to place, reduce dependence on one bookmaker, and let strategies target the best available prices. Available odds, limits, and acceptance remain controlled by each bookmaker. Two concrete advantages: betting at all your bookmakers within the same few seconds locks in prices before odds move in response to your first bet, and per-bookmaker win limits multiply — a $1,000 win limit at 10 bookmakers is a $10,000 effective limit. ### Will bookmakers recognise I'm using a bot? Betmatic drives real browser sessions with human-like behaviour, randomised delays, and randomised daily start/stop times, and is continuously tested against the strongest bot-detection software in the industry. That engineering is proven at scale: Betmatic has processed **more than $320 million in turnover** to date. Bookmakers do also profile *betting patterns* (win rates, stake sizes, timing) regardless of how bets are placed — spreading activity across bookmakers and sensible stake and delay settings keep your accounts looking like any other winning punter's. ## Bets and results ### Why didn't my bet place? Work down this checklist — it covers nearly every case: 1. **Was a session running?** Bets only go to sessions that were online at that moment. Check [Bookmaker Sessions](/documentation/bookmaker-sessions/overview.md) and the machine's status on [Machines](/documentation/website/machines.md). 2. **Was it a manual bet?** A bet you create on the website only reaches sessions that have **Manual** ticked in their Tipster Filter in the bot (it is on by default). See [Troubleshooting](/documentation/bot/troubleshooting.md#bot-not-receiving-bets). 3. **What does Bet History say?** Find the placement on [Bet History](/documentation/website/bet-history.md), filter **Bet Result** to Rejected or Pending, and read the **Note** column — it carries the actual reason (rejection message, insufficient balance, a filter that blocked the bet). 4. **Did the odds fail your check?** Expand the row and compare **Notification Odds** with your minimum-odds settings — if the price drifted below your floor before submission, the bot correctly skipped it. 5. **Was the balance enough?** An account whose cash (or bonus) balance is below the stake is skipped. 6. **Did it arrive too late?** A bet reaching the bot after the race jumped, or outside a configured betting window, is not placed. Still unexplained? Open **View Machine Logs** on the bet's row in [My Bets](/documentation/website/my-bets.md) for the step-by-step account, and see [Troubleshooting](/documentation/bot/troubleshooting.md). ### How do tips turn into bets? Through **Tip Connect**. When you subscribe to a tipster package and configure it on the [Tip Connect](/documentation/website/overview-1.md) page, each pick the tipster publishes is delivered to your account as a bet notification, filtered through your per-package preferences (stake, odds limits, markets), and sent to your running sessions for placement — no manual step in between. The resulting bets appear in [My Bets](/documentation/website/my-bets.md) with the package name in the Source column. See [Package Settings](/documentation/website/overview-1/package-settings.md) for the controls that decide which picks actually get bet. ### What is the difference between My Bets and Bet History? My Bets shows one notification for each instruction sent to Betmatic. Bet History shows the individual placement attempts generated from that instruction, usually one record per bookmaker session. For example, one notification sent to five sessions can produce five Bet History records. See [My Bets](/documentation/website/my-bets.md) and [Bet History](/documentation/website/bet-history.md). ### Why is a bet marked In Review? In Review is not an error: the bookmaker has accepted the bet submission but is holding it for manual review before confirming or rejecting it. Wait for the bookmaker's decision — do not re-submit the bet in the meantime, as that could create a duplicate. See [Troubleshooting](/documentation/bot/troubleshooting.md#bet-shows-in-review-in-bet-history) for why bookmakers do this and what to check. ### Can I schedule a bet? Yes. A scheduled bet can trigger automatically at a specified time or remain saved until you trigger it manually. The relevant bot and bookmaker sessions must still be available when the bet is triggered. See [Scheduling](/documentation/placing-bets/scheduling.md). ### Can I test without placing real bets? Yes. Use the **Simulation** tab on the My Bets or Tip Connect page. Simulated activity is recorded without submitting a real wager to a bookmaker, and you can supply a virtual balance for testing. ### Can I use my own model or strategy? Yes. Your model can use the REST API to retrieve event data, create bets, target sessions, and review results. See the [API Overview](/documentation/api-reference/overview.md) and [worked examples](/documentation/placing-bets/bet-examples.md). ### Can I create a bet from my phone? Yes. The Betmatic website works from a mobile browser, so you can create bets, monitor results, and manage sessions from anywhere. The bets themselves are placed by whichever machine is running the bot at home — see [Creating a Bet](/documentation/website/creating-a-bet.md). ### Can I cancel a bet I placed by mistake? An immediate bet cannot be recalled once submitted — it goes to your running sessions within seconds. Only **Scheduled** and **Market Open** bets have a cancel window: they show a CANCEL action on [My Bets](/documentation/website/my-bets.md) until they trigger. ### What if two of my packages tip the same horse? Each package's matching runs independently, so both can generate a bet on the same selection. The per-session **Allow duplicate bets** setting (off by default) blocks the second bet on the same selection at the same session — see [Bot Settings](/documentation/bot/settings.md). ### Will I be told if a bet fails? There is no failure alert today — email notifications cover new picks, forum replies, news, and unsuccessful payments, but not bet failures. Check [My Bets](/documentation/website/my-bets.md) and [Bet History](/documentation/website/bet-history.md) after race time; the Note column and **View Machine Logs** show what happened. ## Partner Bot ### How do I get a partner access code? Partner access codes are issued by approved partners — you receive one directly from the partner you work with. If a code will not redeem, contact . See [Partner Bot](/documentation/partner-bot/overview.md). ### Why is my Partner Bot quiet? Work through three checks: are the readiness checks all green (see [Readiness](/documentation/partner-bot/readiness.md)), are your sessions turned on, and does the partner actually have promotions scheduled today? A Partner Bot with nothing scheduled is normal — activity follows the partner's promotion calendar. ### What does bonus betting cost? Bonus betting turnover is charged a flat **2.5% Bot Fee**, billed the same way as your other Bot Fees. See [Pricing](/documentation/getting-started/plans.md). ## Access and billing ### How much does Betmatic cost? There is one subscription, from $199 per month. Usage-based Bot Fees apply to cash turnover above $10,000 per month, and bonus betting turnover is assessed separately. See [Pricing](/documentation/getting-started/plans.md) for the progressive rates and billing details. ### How do I get WebSocket access? Private WebSocket access is enabled on request. Email from your Betmatic account email. See the [WebSocket documentation](/documentation/real-time/websocket.md). ### Where can I get help? Check [Troubleshooting](/documentation/bot/troubleshooting.md) for common bot and session issues. If the problem remains, email with the approximate time of the issue, affected bookmaker and Display Name, relevant Log messages, and your bot version.