Bybit API permissions for Neron Signals

1. Create a dedicated API key on Bybit

Open API Management from your Bybit account and create a new key. Use a name that makes its purpose clear, such as your Neron connection. Follow Bybit’s current security verification and key-creation instructions; the available options can depend on the account.

The Neron connection uses an API key and API secret. Follow the supported key type in the connection instructions rather than assuming a self-generated RSA key is interchangeable. Keep the secret in a secure place and enter credentials only in the application’s dedicated form.

2. Match permissions to the intended trading task

For the Neron strategy-following futures bot, the readiness check expects Read and Write access and checks Contract Trade permissions. Order and Position are the relevant contract permission names returned by Bybit. Read-only access cannot authorize live order placement.

Enable the trading and account access required by your supported connection. Withdrawal permission is not needed for the Neron trading workflow. Do not enable unrelated permissions to solve an unclear error; first identify which check failed and why.

3. Check IP restrictions and key validity

If the key is restricted by IP, the allowed addresses must match the service making the API request. Your phone or home internet address is not automatically the address used by a server-based trading connection.

Use the current Neron connection instructions or ask support for the correct allowlist before changing restrictions. Do not guess an IP or remove a restriction simply to silence an error. Review Bybit’s current expiry and validity settings for your key type, especially if a previously working connection stops responding.

4. Save the connection and run the permission check

Sign in to Neron, open the bot’s API settings, and enter the key and secret from the same Bybit account. Save the connection and use the API check control. Inspect the reported trading, contract, and connection conditions individually.

An API check helps identify missing credentials, a read-only key, contract-access issues, IP restrictions, or validity warnings. It does not submit a test order or promise that a later order will fill. Balance, margin mode, exchange minimums, account eligibility, and the order request still matter.

5. Investigate the specific error before retrying

For a read-only warning, revisit the key’s intended trading permissions. For a Contract Trade warning, inspect Order and Position access. For an authentication error, check that the key and secret belong together and that the account and environment are correct.

For an IP error, compare the allowlist with the current supported connection instructions. If the exchange rejects a trading request, retain the error code and time while removing all credentials from anything you share with support.

If an order request times out or its outcome is uncertain, inspect the exchange’s orders and positions before sending another order. A network error alone does not tell you whether the exchange accepted the first request.