Custom connectors
How custom market-data and exchange connectors fit into Barfinex through Provider-managed configuration.
Overview
Custom connectors extend the set of exchanges, brokers, or data sources that Provider can work with. Public clients should treat connectors as Provider-owned configuration, not as direct downstream service integrations.
Public Contract
A connector should define:
- display name and supported market types;
- supported symbols or discovery behavior;
- required credential fields, stored through secure connector settings;
- supported capabilities such as candles, balances, orders, or market data;
- health and diagnostics surfaced through Provider.
Do not send API secrets in public examples or request bodies. Use the secure connector settings flow provided by the current deployment.
Integration Flow
- Create or select a Provider connection.
- Add connector configuration through the documented Provider/Studio surface.
- Store credentials in the deployment secret store or secure connector settings.
- Verify connector health through Provider.
- Use Provider APIs for symbols, candles, orders, balances, and runtime data.
Developer Notes
Exact package names, TypeScript interfaces, internal libraries, and runtime adapter contracts belong to the trading workspace source and internal docs. Public documentation should link to Provider OpenAPI for the current external surface.