Track the interfaces your integration uses.
Follow the versioned interface and capability configuration agreed for your institution.
API v1 reference
The reference covers customer financial resources, institutional identity, Console operations, exchange workflows and market-data reads. Each operation has a dedicated page with its authentication model, request fields and response definitions. This is documentation coverage, not a dated service-release history.
Contract compatibility
Preserve documented field types, amount scales, resource IDs and error codes. Read instrument capabilities before selecting an order instruction. Unknown response metadata should not break an otherwise compatible client; required application fields still need validation.
Plan for interface changes
Use the contract version and enabled capabilities provided to your institution. Coordinate changes to credential scope, permissions, event subscriptions or accounting workflows with your integration owner. Do not infer that a newly documented operation is automatically enabled for every institution.