Connect exchange accounts through a controlled API workflow.
Evolution Zenith is designed to connect supported cryptocurrency exchange accounts with the platform workspace, enabling balance synchronisation, strategy monitoring and eligible order routing through user-controlled API permissions.
- API-based account connection
- User-defined trading permissions
- Balance and position synchronisation
- Connection removal and key revocation
Only the minimum permissions required for the intended workflow should be enabled.
Keep the exchange account and platform roles separate.
The exchange remains responsible for account custody and trade execution. Evolution Zenith provides the connected workspace, strategy logic and monitoring layer, while the API key defines what information and actions may pass between the two systems.
- ✓ The exchange account remains governed by the provider’s own terms and controls.
- ✓ The API key should contain only the permissions required for platform use.
- ✓ Removing or revoking the key should stop future platform communication.
Maintains the exchange account, assets and provider-side security settings.
Verifies credentials and applies the permissions selected by the account owner.
Organises balances, positions and trading activity inside the workspace.
Checks strategy conditions and risk rules before an action becomes eligible.
Receives a permitted order request and processes it under provider conditions.
Enable only the access required by the trading workflow.
API permissions determine what the platform can read or request. The final availability and naming of permissions depend on the connected exchange and account type.
From API creation to verified account synchronisation.
The connection process separates provider-side credential creation from platform-side validation and account monitoring.
Open API settings
Access the API management area inside the supported exchange account.
Create an API key
Generate credentials dedicated specifically to the Evolution Zenith connection.
Select permissions
Enable only the read and trading functions required by the intended platform workflow.
Validate the connection
Add the credentials to the platform and confirm that the account responds correctly.
Review synchronisation
Check balances, permissions and connection status before activating a strategy.
Bring exchange data into the platform without merging account control.
Synchronisation allows relevant exchange information to appear inside the platform while the connected provider continues to maintain the source account and its execution records.
Synchronised account data
Illustrative connection status and information categories.
Account information is refreshed through the available provider connection and displayed in the workspace.
Removing the platform connection should be followed by revoking the corresponding API key at the exchange.
Functions may differ between providers and account types.
The comparison below explains which connection elements are generally required and which remain dependent on the exchange.
| Integration element | Requirement | Configured by | Purpose | Important limitation |
|---|---|---|---|---|
| API credentials | Required | Exchange account owner | Authenticate the platform connection | Must be stored and handled securely |
| Read permissions | Required | Exchange account owner | Synchronise balances and account information | Available data differs by provider |
| Trading permission | Optional | Exchange account owner | Enable manual or automated order routing | Not required for monitoring-only use |
| IP restrictions | Provider dependent | Exchange account owner | Limit where API requests may originate | Support differs by exchange |
| Withdrawal permission | Not required | Exchange account owner | Not needed for standard platform functions | Should remain disabled where possible |
| Order-type support | Provider dependent | Exchange provider | Determines available execution methods | Not every provider supports identical orders |
Protect the connection at the platform, exchange and credential levels.
Integration security depends on more than one system. The user, the exchange provider and the platform each control a different part of the connected workflow.
API key protection
Use a dedicated key, avoid unnecessary permissions and replace credentials if exposure is suspected.
- Do not reuse unrelated API credentials
- Keep withdrawal permissions disabled
- Revoke old or unused keys
Exchange security
Protect the source account with the authentication and session controls provided by the exchange.
- Enable two-factor authentication
- Review account and API activity
- Apply IP restrictions when supported
Connection monitoring
Review connection state, permission changes and unexpected order activity through the platform workspace.
- Monitor synchronisation failures
- Investigate unexpected activity
- Disconnect the account when required
Questions about exchange API connections.
Review account custody, permissions, synchronisation and connection removal before linking an exchange.
How does Evolution Zenith connect to an exchange?
Does Evolution Zenith need withdrawal permission?
Where are connected funds held?
Can the platform work without trading permission?
How is an exchange connection removed?
Are all exchanges supported in the same way?
Connect exchange accounts without giving up permission control.
Use a structured API workflow for account data, trading execution and connection monitoring inside the Evolution Zenith platform.
Risk warning: Exchange integrations depend on third-party APIs, account permissions, provider availability and technical infrastructure. API interruptions, execution delays, rejected orders or incorrect permission settings may affect trading activity. Interface values shown on this page are illustrative and should not be treated as live account information.