Pokémon TCG API
/v2/* version retirement
Stops workingSubscribe to Pokémon TCG APIShare
On March 1, 2027, the Pokémon TCG API will retire its /v2/* endpoints. Requests sent to these endpoints will fail after that date. The change affects all developers calling the v2 API.
Calls it hits
/v2/*
What to use instead of these calls
Migrate your calls to the Scrydex API using a Scrydex API key before the shutdown date. Moving requires more than updating an endpoint, as Scrydex is a separate product with its own accounts, keys, and plans.
Scrydex is a separate product with its own account, keys and plans.
In Pokémon TCG API's words
Developers currently using the Pokémon TCG API should migrate to Scrydex before March 1, 2027.
Facts
- API
- Pokémon TCG API
api.pokemontcg.io - Kind
- Version retirement
- Takes effect
- March 1, 2027
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Pokémon TCG API's own pages
Questions
When does this change take effect?
Calls to /v2/* on Pokémon TCG API stop working on March 1, 2027.
What happens to calls after March 1, 2027?
They fail from that day.
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.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix before March 1, 2027.