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

Create the key inside the dedicated Standard Subaccount. Confirm no Withdraw permission and required Contract Order/Position permissions.

04

Step by step

  1. 01Open Client Portal and choose Connect Exchange.
  2. 02Select the correct Bybit environment.
  3. 03Enter a recognizable label, API key and API secret.
  4. 04Submit once and wait for the security check.
  5. 05Read the result before continuing to bot deployment.
05

What you should see

A safe key returns a VERIFIED connection with a masked key. Raw secrets are never shown back to the browser.

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

Choose the engine that matches your return, cadence and capital profile.