# /v2/* stops working on legacy API keys

Calls to /v2/* on Coinbase App API stopped working on February 5, 2025.

On February 5, 2025, calls to /v2/* stopped working for requests using legacy API keys. Coinbase App API expired all legacy API keys, causing affected requests to fail.

## What to use instead

Create a new CDP API key on the CDP Portal and update deployments with the new secret. Switch request authentication to a JWT bearer token using Authorization: Bearer instead of the legacy CB-ACCESS-KEY and CB-ACCESS-SIGN HMAC headers.

A new CDP API key must be created on the CDP Portal and the secret replaced in deployment.

- API: Coinbase App API (api.coinbase.com)
- Kind: Behaviour change
- Announced: January 22, 2025
- Takes effect: February 5, 2025
- Calls after that day: fail
- Calls it hits: `/v2/*`
- Who it affects: legacy API keys
- Source: [Announcement](https://docs.cdp.coinbase.com/coinbase-app/authentication-authorization/legacy-keys)
- Verified: November 6, 2026, against Coinbase App API's own pages
- Page: https://www.okapi.bot/providers/coinbase-app-api/breaking-changes/v2-stops-working-on-legacy-api-keys/

## Coinbase App API's words

> In February, 2025, we expired all legacy API keys. Create new CDP API keys and update your code to continue using Coinbase App APIs.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent