Bybit EU - API keys not valid for spot - on local version

When attempting to connect a Bybit EU account to a local instance of Gainium, the system returns a validation error stating the API keys are not valid for Spot trading, even when all correct permissions (Spot, Trade, etc.) are enabled on the exchange side.

Environment

  • Version: Gainium Local (latest)

  • Exchange: Bybit EU (SATOS/European entity)

  • OS: Windows 11 / Podman

Steps to Reproduce

  1. Open the local Gainium dashboard.

  2. Navigate to Exchanges > Add Exchange.

  3. Select Bybit SPOT as Exchange

  4. Select https://bybit.eu as Bybit origin.

  5. Enter the API Key and Secret generated on a Bybit EU account.

  6. Click Save/Connect.

Expected Behavior

The exchange should be added successfully, recognizing the Spot trading capabilities of the Bybit EU account.
I also expect that at least an entry is added and maybe with an exclamation mark that something is wrong, but it should be added to the list, to correct it later if something is wrong

Actual Behavior

An error message appears: API keys not valid for spot. The exchange cannot be added to the dashboard.

Thank you for reporting this issue. We have received your bug report regarding the Bybit EU API keys not being valid for Spot trading on the local version of Gainium. We will investigate this promptly and provide an update as soon as possible.

This is the Bybit EU screenshot of the API key:

Screenshot of the error message:

Did you follow this guide? Connect to Bybit - Help Center | Gainium

Take into account that you cannot select “Connect to third party apps” as that would apply the IP whitelist of our hosted version. You need to add your server IP instead.

Connect to third party apps is the only option:

Ouch, that limitation is on Bybit side. Unfortunately we cannot do anything until they allow to create API keys with a custom IP whitelist. Not sure if that restriction is deliberate or just haven’t completed, as the addition to the API is relatively new in .eu domain.

1 Like

I’ve requested support via Bybit on this topic. I was running into the same issue (I like to run it local) and couldn’t figure out the reason, it looked to me that the IP was simply blocked.

Awaiting the next 7 days for a reply