Thank you, I did go and upvote that feature request.
I’m not sure that the endpoint you mention helps in all cases–for example, if someone is invited to OrgA and then some time later to OrgB, I would see both of those in the response but I wouldn’t necessarily know which org invite is the one that was just clicked on. To do that, I’d want to be able to have that “baked in” to the invite ID and then returned with the actions.
Alternatively, or possibly in addition, it would be good if the user_metadata could also be kept as part of the invite and then copied into the user when they actually do get created.