Nice to have:
Approvals API response data would have further utility if the policy which generated the approval was included, or, that policy’s “Scope” metadata was included.
Since approval policies can be scoped, it would be great to have that scope included in the API response. Currently no policy - or scope metadata - is returned by the api/approvals endpoint.
Routing of approval notifications using email jobs & scripts would be much more versatile if scope could be gathered on the first API call, without also needing to call the API for the approval itself, and then call the API for the instance or application to get the properties that provide scope.