Blog

Coinbase Legacy API Keys Are Expiring – Here’s How to Stay Connected in Bitwave

Bitwave

Coinbase Legacy API Keys Are Expiring – Here’s How to Stay Connected in Bitwave
With our streamlined solution, you’ll have your Coinbase data syncing again in no time.
Table of Contents
Crypto accounting, simplified.
Schedule a Demo

On February 5, 2025, Coinbase began expiring all legacy API keys used for retail account connections.

To keep your API access live, you’ll need to generate a new API key through the Coinbase Developer Platform (CDP).

This update enhances security and improves API integrations. But it also means any connections relying on old keys will stop receiving new data.

What This Means for Bitwave Users

If your Coinbase integration in Bitwave was set up with a legacy API key, your data will no longer sync automatically once that key expires.

Don't worry, though – we’ve built a fast, self-serve way to restore your Coinbase connection in just a few minutes.

Follow these simple steps:

Step 1: Create a New CDP API Key

  1. Go to Coinbase API Settings.
  2. Click "Create API Key."
  3. Follow the prompts to generate and download your new key.

Step 2: Update Your API Key in Bitwave

  1. Log in to Bitwave.
  2. Navigate to Wallets and Connections.
  3. Click the Connections tab.
  4. Find your Coinbase Retail connection and select Update Credentials.
  5. Enter your new API key and save.

Bitwave Keeps You Ahead

Bitwave works closely with platforms like Coinbase to anticipate key updates and make transitions smooth for our users.

With our streamlined solution, you’ll have your Coinbase data syncing again in no time.

Questions? Reach us at solutions@bitwave.io.

For more details on creating CDP API keys, visit Coinbase’s official documentation.

Pioneering digital asset accounting teams use Bitwave
Schedule a Demo
G2 High Performer Winter 2024G2 Momentum Leader Winter 2024

Disclaimer: The information provided in this blog post is for general informational purposes only and should not be construed as tax, accounting, or financial advice. The content is not intended to address the specific needs of any individual or organization, and readers are encouraged to consult with a qualified tax, accounting, or financial professional before making any decisions based on the information provided. The author and the publisher of this blog post disclaim any liability, loss, or risk incurred as a consequence, directly or indirectly, of the use or application of any of the contents herein.