# Migration v33 Contains breaking changes as this is migrating the transition API to new API in `transition.ts` ## What do you need to do? 1. Request X-Api-Key from `#api-gateway-support` Slack channel for `“*Subscription Transition API”.*` 2. In the consumer app add the following to the `membership config` file if it's not already there: update the Production Config to read `MEMBERSHIP_TRANSITION_API_KEY_{ENV}` for example `transitionApiKey: process.env.MEMBERSHIP_TRANSITION_API_KEY_PROD` and Test Config to `transitionApiKey: process.env.MEMBERSHIP_TRANSITION_API_KEY_TEST` (you are changing the value of `transitionApiKey` to be that of the new key issued in step 1). This key is already there in some of the consuming apps which means you are to update the vault value with the key issued by `#api-gateway-support` Slack channel timely after successful deployment. To avoid much delay you can update the heroku config variable `MEMBERSHIP_TRANSITION_API_KEY_{ENV}` with the key issued by `#api-gateway-support` Slack channel before updating vault for a quicker transition to the new API. 3: If your CI uses the env vars, you will need to apply changes in step 2 to the relevant file (`cypress/plugins/setup.js` in `next-retention`). ## Changes Update subs-transition API base URL in to `https://api-t.ft.com/subs/transitions>*` for test from `https://api-t.ft.com/transitions>*` and `*