Changelog #2 · Week of 19–23 October 2026

Changelog #2 — Billing in the console, accounts that recover, and more

Week of 19 October 2026: billing you can finish in the console, accounts that recover by themselves, the new NO_PRICE error, and SDK updates.

6 min readLeer en español
On this page
  1. Billing you can finish in the console
  2. Accounts that come back, or say why they can't
  3. NO_PRICE: orders the broker cannot price
  4. Fixes and improvements
  5. Updated SDKs and repos

This is Changelog #2. It covers Saturday 17 to Friday 23 October 2026. The docs changelog stays the complete record, endpoint by endpoint.

This week was about billing you can finish in the console, and about accounts that come back by themselves or say plainly why they can't.

Billing you can finish in the console

  • Card payments show up straight away, even if you close the checkout. Opening Billing or a checkout page now checks your card payment with our payment provider, and while a new plan waits for its first payment we check by ourselves every few minutes. Every renewal that goes through appears in your invoices, with a receipt by email.
  • Pay with another card when a renewal fails. Your plan stays on while we retry the card, and Billing shows Update card and pay. Enter another card on the page (your bank's check, if any, opens over it): it pays for your plan from today and renews it from then on. We cancel the renewal that failed, and if the old card is still charged for it, that charge is refunded automatically. The email about the failed payment and a notice in the console point you there.
  • Confirm a usage charge with your bank, in the console. If your bank asks you to confirm a month-end usage charge (3-D Secure), you get an email and a notice on every console page, and you confirm it on Billing. Nothing is charged until you confirm.
  • Visa and Mastercard. The checkout no longer lists Amex, which our card provider does not take.

Two limits come with usage billing. Both refuse something new; neither changes what you already run.

  • Unbilled usage grows with what you've paid. On a per-account plan, usage beyond the plan's price, such as extra accounts and always-on accounts, is billed after the month. How much of it a workspace can run at once is the plan's price a month ($99 on Production) plus what it has paid in renewals and usage charges in the last 90 days, so it grows as payments go through. Connecting, reconnecting or switching an account to always_on past it answers 402 CREDIT_LIMIT, with the limit in plain words. Changing to a plan that would leave you above its limit answers 409 REDUCE_USAGE_FIRST and says what to switch off or disconnect first. GET /v1/plans shows each plan's pricing.creditLimit.
  • An unpaid usage charge pauses opening, never closing. If a month's usage charge still can't be collected after a week of daily retries, or isn't confirmed with your bank within a month, opening orders, multi-account orders, connecting new accounts and switching to always_on answer 402 PAYMENT_OVERDUE until it's paid. Closing positions, cancelling orders and moving stops always work, and your plan, accounts and history are kept. Billing has Try the card again (up to 3 times an hour), and opening resumes as soon as the charge is paid.

Every billing error code is listed under Billing errors.

Accounts that come back, or say why they can't

  • Always-on accounts come back by themselves. If an always-on account's terminal stops (after maintenance, a crash or a start that failed), it is brought back online within minutes, with no call from you. A refused login, a second factor, a certificate or trading disabled at the broker still waits for you: retrying those is how a broker locks an account.
  • When the problem is ours, accounts say so. If accounts can't come online because of a problem on our side, an account on its way online carries problem.code PLATFORM_ISSUE with no actions, and a failed POST /v1/accounts/{id}/warm says the same: your login is fine and retrying won't help. status.fxapis.com has updates, and its Trading engine row now reflects whether accounts can come online, not only whether our servers are running.
  • starting while an account comes online. A new account you bring online now shows starting instead of staying created. If its terminal stops before it is ready, it shows offline with the reason.
  • A server name MetaTrader can't find is reported as such. The account goes to error with problem.code SERVER_NOT_FOUND, and the console's alert bell says "The broker server could not be found", naming the server. Check the exact server name in your broker's welcome email or in MetaTrader's File → Login dialog, then update the account. Its terminal stays stopped until you do, and an always-on account isn't retried meanwhile.
  • More broker servers in the server search. About 820 MT5 servers of widely used brokers and prop firms (IC Markets, Pepperstone, Exness, XM, HFM, Vantage, VT Markets, Bybit, FTMO, The5ers, Deriv and more) are now offered as you type, by their exact names. fxapis works with any MT5 broker: a server that isn't offered can still be typed exactly as MetaTrader shows it.

See Account states and What is wrong, in words.

NO_PRICE: orders the broker cannot price

When the account's broker has no current price for the symbol (its market is closed, or this broker doesn't offer it), an order now answers 422 NO_PRICE instead of 503 SEND_FAILED. Nothing was sent, as before.

Breaking: SEND_FAILED means "retry now", which couldn't help here. If your code retries on SEND_FAILED, give NO_PRICE its own branch and retry once the symbol is quoting. The same Idempotency-Key may be reused. The SDKs don't retry NO_PRICE on their own.

See The three failures.

Fixes and improvements

Console and support

  • Support from the console. A new Support page lets anyone signed in to a workspace open a ticket and follow the conversation. We answer there and by email. If a card payment fails at checkout or when you update a card, the message links to it.
  • Your trial, on every console page. While your trial runs, a banner shows the days left and when it ends, with Choose a plan; members who aren't the owner are asked to ask the owner. You can hide it for the rest of the day, except in the last three days. We also email you a week, three days and a day before the trial ends, and when it has ended.
  • What an ended trial or plan means, said plainly. Once a trial ends, every console page says so: opening new trades is paused until a plan is chosen, open positions can still be closed and orders cancelled, and your accounts, keys, history and settings are kept. A paid plan that ended says the same. These notices can be hidden for a day at a time.

Plans and billing

  • Always-on accounts follow the plan. When a trial ends, or a plan ends or changes to one without always-on accounts, those accounts are switched to warm_on_demand: they connect when an order needs them and go offline when idle. We tell you by email and in the console, and each switch is listed in the account's events (GET /v1/accounts/{id}/events) as "Connection mode changed".
  • Starter and Scale are no longer sold. They were replaced by Production and Business, and POST /v1/billing/checkout answers PLAN_NOT_PURCHASABLE for them. A workspace already on Starter or Scale keeps it, and its card keeps renewing it, until it changes to a plan from GET /v1/plans.
  • Checkout limits. Starting a checkout is limited to 5 per workspace and 10 per owner's email a day (429 CHECKOUT_LIMIT), and a coupon isn't redeemed while a card payment for a plan is being set up (409 CHECKOUT_PENDING).

API keys

  • New billing:read scope. Reading the subscription, invoices, usage charges, agreement, standing and daily usage now needs billing:read. Keys made before 21 October 2026 that hold accounts:read keep reading them; a key you make now for billing reads needs billing:read. See Scopes.

Updated SDKs and repos

  • TypeScript SDK 0.3.1 (fxapis on npm) adds PLATFORM_ISSUE to problem.code, the billing:read scope and creditLimit on plan pricing. Source: FXapis/fxapis-typescript.
  • Python SDK 0.2.1 (fxapis on PyPI) adds PLATFORM_ISSUE to problem.code and the billing:read scope. Source: FXapis/fxapis-python.
  • If your code switches exhaustively on problem.code or on scopes, handle the new values.
  • fxapis-claude-plugins: the trading-mt5-safely skill knows CREDIT_LIMIT, PAYMENT_OVERDUE and NO_PRICE, and what to do about each.
  • fxapis-integrations: the Postman collection says to resend a SEND_FAILED order only when retryable is true.

That's the week. If something here doesn't behave as described, open a ticket from the console's Support page or write to support@fxapis.com.

— Software architect and AI engineer with more than 15 years of building and scaling software systems. Designs and builds production-grade software and AI systems, and writes about how it's done.

elwizard.netGitHubInstagram

All in this topic
> Connect. Execute. Scale.

Trade MT5 from your own code.

Connect accounts by login, password and server, and place orders over HTTPS. We run MetaTrader 5; you install nothing.