Currently our resolvers don’t handle this type of request (as it’s largely based on our REST implementation) though this will be changing in the future. In your case it would require a custom resolver or at least a customization of the currently implemented one.
Let me ping @alexandrebodin @Convly and @Pierre_Noel to see if they have any suggestions.