This guide covers both paths Hyerlo supports for Binance Futures: live read-only API autosync first, then CSV fallback. Manual entry always works when you need a single correction.
Parent hub: import. Product page: Binance Futures trading journal.
Status at a glance
| Method | Status | Plan note |
|---|---|---|
| Read-only API autosync | Live | Breakout (3 accounts) or Expansion (unlimited) |
| CSV upload | Available | Useful for backfill and key-free workflows |
| Manual entry | Available | Base $0 forever for manual trades only |
| Bybit / Phemex / Hyperliquid / Binance USDM autosync | Coming | CSV for those venues today |
Before you start
- Decide whether you want ongoing sync (API) or a file drop (CSV).
- Use a dedicated read-only key labeled for Hyerlo. Never reuse a trading key.
- If you use subaccounts, connect or export each one on purpose so PnL does not blend.
{/* screenshot: Hyerlo exchanges list showing Binance Futures connected vs CSV venues */}
Path A: read-only API autosync
Create the key on Binance
Steps below follow Binance’s public API Management FAQ.
- Log in to Binance. Complete identity verification, enable 2FA, and make sure the Spot Wallet has received a deposit of any amount (Binance requires this before API creation).
- Open Profile → Account → API Management.
- Choose Create API. Pick a system-generated HMAC key unless you already run self-generated Ed25519 or RSA keys.
- Name the key clearly.
- Pass 2FA / passkey checks.
- Copy the API key and secret immediately. Store the secret in a password manager. You will not see it again.
- Keep Enable Reading on. Leave trading, futures trading toggles beyond reading, withdrawals, and Universal Transfer off.
- Enable the Futures account before key creation when possible. Binance documents that older keys created before Futures activation often cannot add Futures related permissions later.
- Optional: restrict by IP only if your policy demands it. Unrestricted system-generated HMAC keys are limited to reading, which is what Hyerlo needs.
Trust primer: read-only API keys.
Connect inside Hyerlo
- Open the connect-an-exchange flow.
- Choose Binance Futures.
- Paste the read-only API key and secret.
- Confirm the connection and wait for the first sync to land trades in the dock.
{/* screenshot: Hyerlo connect flow for Binance Futures read-only key */}
{/* screenshot: first successful sync showing trades dock populated */}
If sync returns empty, confirm you traded on the Futures account tied to that key, and that the key was created after Futures was enabled.
Path B: CSV fallback
Use CSV when you want history before the key existed, when a sync gap needs a patch, or when you will not store any key.
Export from Binance Futures
Binance publishes support material for downloading USD-M and COIN-M Futures order and trade history. Exact menu labels move over time, so treat this as a checklist against the live Binance UI:
- Open Binance Futures for the product you trade (USD-M or COIN-M).
- Open the Orders / Trade History area (not Wallet deposits).
- Select Trade History or fill history for the dates you need.
- Export or generate a CSV. Prefer executed fills over open or cancelled orders.
- If the date picker caps the window, export several adjacent files.
- Keep originals in a dated folder.
{/* screenshot: Hyerlo CSV upload dropzone awaiting a Binance Futures file */}
Upload in Hyerlo
- Open CSV import.
- Upload the Binance Futures file.
- Check the preview for time, symbol, side, price, size, fee, and realized fields.
- Finish the import. Re-run for each date slice or subaccount.
{/* screenshot: CSV preview table with mapped Binance Futures columns */}
After import or sync: what should appear
- Fills in the trades dock
- Chart marks for entry and exit once the trade is closed and reviewable
- Fee fields available for the trading vs funding widgets once funding data is present
- Room for tags, notes, setups, and themes on each trade
Open positions may sync as positions without a finished review story. Journal closed work first if you are reconciling a week.
Pitfalls
| Pitfall | What to do |
|---|---|
| Trading-enabled API key | Delete it. Create a reading-only key. |
| Key created before Futures activation | Create a new key after Futures is on. |
| CSV of open orders only | Re-export trade or fill history. |
| Overlapping CSV windows | Rely on duplicate protection, still keep file dates. |
| Mixed Spot and Futures rows | Keep Futures exports separate. |
| Timezone confusion | Note whether timestamps are UTC, then review the calendar in one zone. |
Verify the first sync or import
Spend five minutes after the first load. It saves a messy month later.
- Pick three closed trades you remember and match symbol, side, and size in the dock.
- Open one on the chart. Entry and exit marks should sit on the candles you traded.
- Check fee fields. Trading fees should appear when the exchange sent them. Funding may arrive on a different cadence than fills.
- Add one tag and one note on a trade so you confirm write access on the journal side.
- If you connected a key, place a tiny intentional paper note in your own records with the key label and creation date. Revoke that key immediately if it ever gains trading rights by mistake.
{/* screenshot: single trade review with tag and note panel open */}
When to prefer CSV over the key
- You are importing a year of history before you created the Hyerlo account.
- Your security policy forbids third-party keys even when they are read-only.
- You are reconciling a known sync gap against an exchange statement.
- You trade rarely and a monthly file is simpler than managing secrets.
For active discretionary traders who review every week, autosync removes the export chore. The journal stays current without a weekly download ritual.
Manual corrections
Base is enough to type a missed fill. Paid plans keep manual entry beside autosync. Use it for liquidations you want annotated, or for a partial fill the export skipped.
Pricing reminder
- Base: $0 forever, manual trades only
- Breakout: $15/mo ($11 launch), 3 autosync accounts
- Expansion: $30/mo ($22 launch), unlimited autosync
- Launch pricing: first 100 members or until Dec 31 2026
Frequently asked questions
Is Binance Futures autosync actually live?
Yes. Read-only API autosync for Binance Futures is live. Bybit, Phemex, Hyperliquid, and Binance USDM remain CSV only, with autosync coming.
Can Hyerlo withdraw or trade with my key?
No. Use Enable Reading only. Hyerlo is a journal, not an execution bot.
Do I still need CSV if autosync works?
Only for backfill, audits, or gaps. Many traders connect the key and keep a monthly CSV archive anyway.
Where do I read about other venues?
Start at the import hub, then the matching journal leaf such as Bybit.
Related pages
Connect the read-only key when you can. Fall back to CSV when you must. Then review on the chart. Try hyerlo.com.