Current State: 

To link a deployment key obtained from the Lifetime API with the Lifetime user interface, it is currently necessary to map the platform entity osltm_staging to retrieve the staging id. This id is then used as a parameter in the Lifetime URL, as shown below:

<lifetimehost>/lifetime/Staging_Progress.aspx?StagingId=<StagingId> 

Suggestion for Improvement:

I propose two possible enhancements to facilitate the process:

Option A:

Allow the Lifetime deployment screen to accept the deployment key directly as an input parameter.

Option B:

Modify the Lifetime API to include the StagingId in its response.

Implementing either of these options would simplify accessing deployment information, for companies utilizing the LifetimeAPI in their internal deployment processes. While acknowledging that a fully automated CI/CD pipeline takes away the need for the Lifetime interface, integrating these features would still benefit cases where the Lifetime API is used to enhance rather than fully automate deployment processes.