I would say, however, that this is a bit of a hack, in that you have to (1) Add an HTTP Header for Content-Type = application/x-www-form-urlencoded, and (2) set the HTTP Entity to a string using application/x-www-form-urlencoded that you’re responsible for encoding yourself. In this case, it’s pretty simple since that string is just one key/value pair and there’s no special characters that need to be escaped. I think we need more direct support in the REST Post snap for this encoding. The “Upload body type” should include an option corresponding to this content type and the snap should automatically build a properly-encoded string from the input entity if it’s an object (it could just encode that object’s key/value pairs).