01

What you are doing

You are submitting the Standard Subaccount API key and secret to an encrypted server-side validation flow.

02

Why it matters

HEDGERON checks account scope, trading permissions, Unified account mode and prohibited permissions before saving a connection.

03

Before you start

Read the current strategy card at the top of Step 3. It names the strategy, market and exact capital for the subaccount required now. Use one dedicated Standard Subaccount per strategy.

04

Step by step

  1. 01Open the named dedicated Standard Subaccount in Bybit.
  2. 02Create the API key inside that subaccount, with Contract Order and Position permissions and no Withdraw permission.
  3. 03Return to Step 3. Confirm that the strategy name and required capital match this subaccount.
  4. 04Paste that subaccount’s API key and secret, tick the dedicated-subaccount confirmation and press Next: verify connection.
  5. 05If a six-digit security confirmation appears, enter the current HEDGERON authenticator code on the same page.
  6. 06After Connection verified appears, press Next: review.
05

What you should see

A safe key returns Connection verified for the named strategy. The secret disappears from the form. The Next button opens the review for this same strategy.

06

Security check

A Main Account key, Withdraw-capable key, read-only key or key missing required trading permissions must fail closed.

07

Common problems

Connection failed

Check exact key/secret, environment, IP whitelist, account mode and Bybit service status.

Security check failed

Create a new minimum-permission key instead of weakening HEDGERON security rules.

08

Next step

Press Next: review. Do not connect the second or third subaccount until onboarding names that strategy.