Skip to main content

Bybit API connection – troubleshooting for Upcomers

Important: The Bybit platform is no longer available at Upcomers. All previously purchased Bybit accounts remain active and can continue to be used according to the existing rules.

This guide covers API connection issues for previously purchased Upcomers accounts on the Bybit demo environment.

Quick checklist

  • Using Bybit Demo, not Live

  • API key = Read/Write, Unified, Assets

  • No IP restrictions on the key

  • When linking a new API key for an existing Bybit account, the subaccount must be fresh, with no previous trades or balance movements

  • No open positions or pending limit orders

  • API key not edited, rotated or deleted after linking

  • The key is unique to every challenge phase, not reused elsewhere

  • Keys copied via Copy button, not typed

Common issues and fixes

1) Connected to the wrong environment

Symptom: Account will not sync or shows empty balances.

Cause: Live API used instead of Demo.

Fix: Create a Demo subaccount API key on Bybit and reconnect it in Upcomers.

2) Missing required permissions

Symptom: Partial data, orders fail to register.

Cause: API not set to Read/Write, Unified, Assets.

Fix: Regenerate the API with Read/Write + Unified + Assets enabled, then relink.

3) IP restrictions enabled

Symptom: Connection denied or times out.

Cause: API created with IP whitelist.

Fix: Create the key with No IP restrictions and connect that key.

4) Keys copied incorrectly

Symptom: “Invalid key” or “Signature error.”

Cause: Manual typing, extra spaces or missing characters.

Fix: Use Bybit’s Copy button for both the API Key and Secret. Reconnect.

5) API modified or deleted after linking

Symptom: Connection suddenly stops working.

Cause: Editing permissions, rotating or removing the key.

Fix: Create a new key with the correct settings and relink it in Upcomers.

6) Open trades or pending orders block the link

Symptom: Linking fails or throws a generic error.

Cause: Active positions or limit orders on the Bybit side.

Fix: Close all positions and cancel all open orders, then connect the API.

7) API key reused across challenge phases and/or different accounts

Symptom: Conflicts between accounts or wrong data shown, inability to link keys to account.

Cause: Same key linked to another challenge previously.

Fix: Generate a fresh API key for each challenge and link it only there.

Did this answer your question?