Axcera

If your firm runs on Axcera, Rubi syncs traders, accounts, trades and payouts from the Axcera Open API with a read only key.

Native connector

What you need#

Setting	Value
Base URL	`https://openapi.<tenant>.app.axcera.io`
API key	Created in the Axcera back office, with read access to customers, accounts, trades and payouts.
Account scope	Optional JSON to limit the sync to some plan categories or platforms.

Connect#

In the Axcera back office, create an Open API key for Rubi and copy it.
In the Rubi dashboard, open Integrations and choose Connect Axcera. Paste the base URL, for example https://openapi.examplefirm.app.axcera.io, and the key.
Optionally restrict the scope, then run the live check. Each probe shows its status, latency and a hint when something fails.
Save. The first backfill starts immediately.

optional account scope

{ "plan_category_ids": [12, 14], "platforms": ["mt5", "ctrader"] }

IP allowlist#

Rubi calls Axcera from fixed egress ranges shown under Integrations in the dashboard, each with a copy button. If your Axcera tenant restricts API access by IP, add them before running the check.

What is synced#

Resource	Used for
Traders	Profiles, KYC state and tags in the Rubi CRM, matched to interviews.
Accounts	Program, phase, status, balances. Interviews can focus on one account.
Trades	Closed and open positions, the basis of the deterministic activity analysis.
Payouts	Requested and paid payouts, shown on the trader profile and in reports.

Rubi runs an initial backfill, then incremental syncs every 5 minutes by default (configurable from 1 to 60 minutes) using the updated time with an overlap, so nothing is skipped. Rubi never writes to Axcera.

Sync health, the last error with its endpoint and HTTP status, and every sync run are visible on the integration card. Failures also emit integration.sync_failed webhooks.