Coinbase App API
/v2/* stops working on legacy API keys
Stopped workingSubscribe to Coinbase App APIShare
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.
Calls it hits
/v2/*
What to use instead of these calls
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.
In 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.
Facts
- API
- Coinbase App API
api.coinbase.com - Kind
- Behaviour change
- Announced
- January 22, 2025
- Takes effect
- February 5, 2025
- Calls after that day
- Fail
- Who it affects
- legacy API keys
- Source
- Announcement
- Last updated
- Verified
- , against Coinbase App API's own pages
Questions
When does this change take effect?
Calls to /v2/* on Coinbase App API stopped working on February 5, 2025.
What happens to calls after February 5, 2025?
They have failed since February 5, 2025.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Coinbase App API 5
-
PUT /v2/userEndpoint removal Stopped working -
GET /v2/users/{id}Endpoint removal Stopped working -
GET /v2/transactionsEndpoint removal Stopped working -
/api/v3/brokerage/intx/*Endpoint removal Stopped working -
No date
GET /v2/payment-methods*Endpoint removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.