Broker API, CSV or MT5: choosing an IB reporting connection

A partner API follows the partner portal's scope

A partner API can remove repetitive exports when a broker provides the commission and payment records you need. It still needs a defined account scope, pagination, date handling and a way to detect corrections. Before selecting an integration, ask for the schema and a representative anonymized response.

Exness publicly documents a Partnership API and describes a multi-broker partner using it to combine partner-area information on a separate site. That makes it a research candidate for IBDock. It does not mean IBDock has a verified live Exness connector, or that any credential provided to that API is automatically restricted to reading.

Files are a useful first connection

A statement export is often the quickest way to establish a common data model. Files let an IB inspect what is shared and let a product team validate the fields without handling broker credentials. The tradeoff is freshness: yesterday's export cannot tell you whether today's statement was corrected.

CSV is straightforward when the format is stable. Excel needs clear rules for sheets, dates and formulas. JSON is useful for structured snapshots but is still a file, not an automatic API connection. A custom broker export needs a tested field mapping; renaming its extension will not make it compatible.

MT5 access is not one universal permission

An investor login concerns the account it authorizes. A trader account view, an IB commission account and a broker-provided manager/API scope are different sources. Confirm the precise accounts, records and time range available before deciding whether the access answers an IB reporting question.

Do not supply a trading password just to see a demonstration. For a live connector, the broker must confirm the least-privilege permission set and revocation procedure. A system that can read an account balance may still lack the partner attribution or contractual commission records needed for reconciliation.

Ask these questions before connecting

Write down the access scope with the broker and keep the answer alongside the connection. Treat missing information as unknown rather than filling it with a reassuring green status. Test the same connector on a second authorized account before assuming the integration is reusable.

Which entity and partner accounts are included?
Are commissions, payments and adjustments separate records?
Can the provider enforce read-only access?
What timezone, currency and historical range apply?
How are pagination, rate limits and corrected records handled?
How can the IB revoke access and delete stored data?

Make coverage visible after the first sync

A useful connection screen shows last successful sync, reporting period, granted scope and unresolved gaps. A successful HTTP response only establishes that a request succeeded; it does not prove that all commission records were returned. Compare a known portal total and a controlled statement export with the first sync.

In the IBDock public preview, broker selection is a connection-planning tool. Canonical sample files work today. Live broker API and MT5 synchronization remain unavailable until permissions, authentication, storage and data mapping have been verified with a real authorized pilot.

Put the method to work.

Try the sample workspace. No broker password required.

Open the statement templates ↗

Sources and scope

Editorial scope: product reporting guidance with fictional examples. No paid broker placement, investment recommendation or independent audit claim. Product capabilities are described as of the update date shown above.