Migrate from a legacy key to an OAuth key

Last updated: Feb 26, 2024
DEVELOPER

There are two ways to authenticate API requests via Redox: using our legacy API keys or our recommended OAuth API keys. Learn about authentication methods.

Use this guide if you're currently using legacy API keys but would like to migrate to OAuth API keys. Bonus, you can successfully migrate to OAuth API keys without needing a downtime.

  1. Log in to the Redox dashboard.
  2. Make sure that you're in the same environment (i.e., development, staging, production) that your existing legacy API key is in. If you're not in the same environment, select the correct environment from the drop-down field on the top left.
  3. Update your system to use the new OAuth key. Include the Redox-Source-Id header in your API requests with the value of the header set to the ID of your legacy API key.
  4. Once you fully migrate your application to the new OAuth key, rotate the legacy key's secret by generating a new secret value.

You can keep both your legacy API keys and OAuth keys in your system without causing conflicts.