How To Disconnect Your FinRev API

When closing a FinRev account or moving exchanges that you are trading FinRev on, it is best practice to disconnect the previous API connection with FinRev and delete the API key.


The following guide will walk you through the steps on a few of our most popular exchanges - the principles are the same on other exchanges where examples are not provided.


How to Disconnect Your FinRev API From Bybit


  1. Head over to www.bybit.com and click 'Log In'

  1. Type in your email address & password
  2. Click 'Log In'

  1. Hover your mouse over the profile icon
  2. Click on 'Switch/Create Account'

  1. Select the subaccount that FinRev is connected to

  1. Once switched to your subaccount, hover your ouse over the profile icon
  2. Click on 'API'

  1. Find the API key that you used to connect your Bybit account to FinRev
  2. Click 'Delete'

  1. Click 'Confirm'

How to Disconnect Your FinRev API From Kucoin



  1. Head over to www.Kucoin.com
  2. Type in your log in credentials (you must log into your main Kucoin account and not a subaccount)
  3. Click 'Log In'

  1. Navigate to the menu on the left of the screen and click on 'Sub-Accounts'

  1. Find the subaccount that is connected to FinRev
  2. Click on 'Settings'
  3. Click on 'View API'

  1. Click on the trash can to delete the API key

How to Disconnect Your FinRev API From Bitget


  1. Head over to www.bitget.com/login
  2. Type in your email address & password
  3. Click 'Log In'

  1. Navigate to the menu on the left and click on 'Sub-accounts'

  1. Find the subaccount that is connected to FinRev & click on 'Settings'

  1. Click on 'API Keys'

  1. Click on 'Delete'

How to Disconnect Your FinRev API From dYdX


  1. Click on the Metamask icon in the top right of the screen
  2. Click on 'Disconnect' to sever the connection between dYdX & Metamask


If you are experiencing difficulties with the steps outlined above, you can contact us at:  [email protected]

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us