IssueTracker

The customer is finding the default 24-hour transition period too short to roll out changes to all applications effectively. They have requested the ability to extend the duration for which the old API key remains active after generating a new key to 1 month.

The customer is seeking a feature that allows them to keep the old API key active for 1 month after generating a new key. This extended transition period would provide their developers with adequate time to update their applications, ensuring a seamless transition without disruptions.

Reasoning:
The customer's request is driven by the need for a longer transition period to avoid disruptions in their applications and provide their developers with ample time to make necessary changes. They believe that extending the transition period to 1 month would significantly enhance their operational efficiency and minimize potential downtime during the migration process.

Use Case:
The extended transition period would benefit not only our customer but also numerous other users facing similar challenges. It would enable businesses and developers to plan and execute their API key transitions more efficiently, reducing the risk of disruptions and ensuring uninterrupted service for their users.

We kindly request your team to consider this feature request. We believe that extending the API key transition period would greatly enhance the user experience for users.

Thank you for your attention to this matter.