Infrastructure & API Access
Understanding where automation runs and why technical architecture is the foundation of secure execution.
01. What an Exchange API Is
An API (Application Programming Interface) allows software to communicate with an exchange account under explicitly defined permissions. APIs do not provide ownership or custody of funds—they provide controlled access to information and order routing.
02. Trade-Only Permissions
The primary security mechanism of an API is the scope of its permissions. Trade-only permissions allow software to place and cancel orders but explicitly prohibit withdrawals or transfers to external addresses.
Enabled
- • Spot/Futures Trading
- • Order Book Access
- • Balance Checking
Disabled
- • Fund Withdrawals
- • Password Resets
- • API Management
03. User-Controlled Infrastructure
Running automation on your own infrastructure ensures transparency. The software executes locally, meaning decisions are made and orders are generated within your environment rather than relying on a third-party server for discretionary control. This architecture prioritizes independence over convenience.
04. Technical Risks & Constraints
No infrastructure is perfect. Automation operates within technical constraints such as network latency, exchange downtime, and API rate limits. These risks cannot be eliminated—only managed through robust error handling and connectivity monitoring.