Kaggle API v2 migration: dataset downloads failing after v1 deprecation

Context

With the Kaggle API v1 deprecated, scripts that previously downloaded datasets using v1 personal API keys now need to move to v2. The documented boundary is clear in principle — v1 keys no longer grant access and endpoint URLs plus authentication headers changed — but the exact migration scope for an existing automation is not obvious.

Goal

I want to keep an existing dataset-download workflow working under API v2 with minimal changes, while understanding exactly which parts of the old setup are now invalid: the credential format, the download endpoint, or both.

Uncertainty

It is unclear whether regenerating credentials produces a v2-compatible key in the same kaggle.json format, or whether the file layout itself changed. I also do not know if the CLI (kaggle datasets download) abstracts the v1/v2 difference entirely, or if direct REST calls in older scripts must be rewritten against new endpoint paths and headers.

Questions

• Does a newly generated API token work transparently with both the current CLI and raw v2 REST endpoints, or are separate credentials required?
• Which v1 endpoint patterns (dataset download, submission) have direct v2 equivalents, and which were removed or renamed?
• Is there a documented deprecation timeline or version-pinned CLI release that still emits warnings rather than hard failures, so I can verify migration progress incrementally?