Aello needs API credentials to read your Leader account and place orders on enabled Followers. The Leader can be your account or someone else's, and its key can come from a main account or a subaccount. Every Follower must use a dedicated exchange subaccount so its owner controls exactly how much money Aello can access. Withdrawal permission is never required.
Aello supports Spot and all Futures markets on Binance and Bybit, including Binance USD-M and COIN-M Futures. Options are not supported. Enable only the market permissions your accounts need.
Before you start
- Enable two-factor authentication on the exchange account.
- Decide whether the key is for Demo Trading or Live Trading. Keys do not cross between environments.
- Choose the Leader account. It can be a main account or subaccount owned by you or someone else.
- Create a separate exchange subaccount for every Follower.
- Create the key on the exchange website, not from a link sent in chat or email.
Create a dedicated subaccount for each Follower
Leader and Follower accounts do not need to share an owner or master account. Aello only watches the Leader and never places orders through the Leader key, so that key can belong to either a main account or subaccount.
Aello does place and cancel orders on Followers. Each Follower must therefore be a dedicated exchange subaccount under that Follower owner's main account. The owner transfers only the funds they want Aello to trade into the subaccount, keeping the rest of their exchange balance outside Aello's reach.
A setup can look like this:
- Leader: your main account, your subaccount, or a friend's chosen account.
- Follower 1: a dedicated subaccount created under its owner's main exchange account.
- Follower 2: a dedicated subaccount created under another owner's main exchange account.
Create a Binance Follower subaccount
- The Follower owner signs in to their Binance main account.
- Open Profile → Dashboard → Sub Accounts → Account Management.
- Select Create Sub Account.
- Choose a virtual email for an API-only Follower, or use a regular email if someone also needs separate login access.
- Give the subaccount a clear label, such as Aello Follower 1.
- If this Follower will copy Futures, enable Futures for the subaccount from its action menu.
- Transfer only the funds intended for this Follower from the main account to the subaccount.
Binance controls subaccount eligibility. If the Sub Accounts menu is missing, check the official Binance subaccount requirements for your account type and region.
Create a Bybit Follower subaccount
- The Follower owner signs in to their Bybit main account.
- Open Profile → Subaccount.
- Select Create → Standard Subaccount.
- Enter a nickname and username that identify the Follower.
- Leave separate login disabled unless another person needs to sign in to that subaccount.
- Complete creation, then transfer only the funds intended for this Follower into the subaccount.
Bybit's official Standard Subaccount guide shows the current creation and management screens.
Choose permissions by account role
| Aello role | Exchange account | Read access | Trading access | Withdrawals |
|---|---|---|---|---|
| Leader | Main account or subaccount | Required | Not required | Off |
| Follower | Dedicated subaccount | Required | Enable only the Spot or Futures markets you will copy | Off |
Keep the Leader key read-only. If you need another Follower later, create another dedicated subaccount instead of granting trading access to a main-account Leader.
Create a Binance API key
- For a main-account Leader, open Profile → API Management. For a subaccount Leader or any Follower, open Sub Accounts → API Management and select the correct subaccount first.
- Select Create API.
- Choose a system-generated HMAC key so Binance gives you an API key and secret that Aello can use.
- Give the key a clear label that matches the account, such as Aello Leader or Aello Follower 1.
- Complete Binance's security verification.
- Copy the API key and secret while the secret is visible.
- Open the key's restrictions and leave reading enabled.
- For a Follower, enable Spot & Margin Trading and/or Futures only for the markets you enabled in Aello. A Leader does not need trading permission.
- Confirm withdrawal permission is disabled.
If Aello runs from a private server or another connection with a stable outbound IP, restrict the key to that IP. Do not add an IP restriction that changes regularly or the exchange will reject Aello when the address changes.
See Binance's official API-key guide if its menu labels differ.
Create a Bybit API key
- For a main-account Leader, open Profile → API. For a subaccount Leader or any Follower, open Profile → Subaccount, find the correct subaccount, then open its Management → API Management.
- Select Create New Key, then choose a system-generated API key.
- Select the option for API transactions rather than a third-party application connection.
- Give the key a clear name that identifies its Aello role.
- Choose Read-Only for a Leader or Read-Write for a Follower.
- For a Follower, enable only the Spot and/or derivatives order and position permissions required by the markets you enabled in Aello.
- Leave withdrawals and asset transfers disabled.
- Add a stable IP restriction when your Aello host has one, then complete two-factor verification.
- Copy the API key and secret before closing the result.
Bybit documents system-generated HMAC keys and environment endpoints in its official API guide.
Add the key to Aello
- Open Aello and add a new exchange account.
- Select Binance or Bybit, then choose the matching Demo or Live environment.
- Add the chosen read-only account as the Leader, whether it is a main account or subaccount.
- Add each dedicated Follower subaccount as a separate Follower.
- Set the account role and enabled markets.
- Paste the API key and secret into their matching fields.
- Save the account and wait for Aello to report a healthy connection.
- Clear the credentials from your clipboard after saving.
Aello encrypts exchange credentials on the machine you control. The exchange secret should never be sent to Aello support.
Troubleshoot connection errors
- Invalid key: confirm the complete key and secret were pasted into the correct fields.
- Wrong environment: a Demo or Testnet key cannot connect to a Live endpoint, or the reverse.
- Permission denied: check read access and the relevant Spot or Futures trading permission.
- IP rejected: update the allowlist to the Aello host's current outbound IP or remove an incorrect restriction.
- Timestamp error: synchronize the computer or server clock automatically.
- Futures unavailable: confirm the derivatives account is enabled at the exchange.
Security checklist
- Use one dedicated exchange subaccount and one API key per Follower.
- Never reuse the Leader's API key for a Follower.
- Use separate keys for Demo and Live environments.
- Keep withdrawal and transfer permissions off.
- Use a stable-IP allowlist where practical.
- Never include secrets in screenshots, chat, email, logs, or support tickets.
- Delete the key at the exchange immediately if it may have been exposed.
- Start in Demo Trading and verify the intended account before using Live Trading.