[Add-ons API]It is recommended to extend the expiration time of Edge extension REST API keys

[Xsy41]

• Problem description

When using the Microsoft Edge extension's REST API (v1.1), I found that the default expiration time for the API key was just over two months. This is inconvenient for long-term automated deployments and CI/CD integrations because API keys need to be manually regenerated and updated frequently.

• Current behavior

The default expiration time for API keys is about two months.
After the expiration, you need to manually re-generate the API key and update related configurations.
No option has been found to extend the API key expiration time.

• Expected behavior

Provide longer API key expiration times (e.g., 1 year or forever).
Or provide an automatic renewal mechanism (such as refreshing tokens via OAuth 2.0).
Added the option to customize the expiration time in the Partner Center.

• influence

Reduced development efficiency: Frequent manual API key updates increase development and operation effort.
Automated interruption: If the API key is not updated in a timely manner, the CI/CD pipeline will be interrupted due to authentication failure.
User experience degradation: For extensions that require long-term maintenance, frequent key management can affect the developer experience.

[captainbrosset]

Thank you for reaching out. This question is specific to Edge Add-ons, not its documentation. Therefore, could you please open a new issue for this over on the dedicated repository at: https://github.com/microsoft/MicrosoftEdge-Extensions ?

Thanks for your understanding.