Our internal Web team are trying out the various REST calls available, and have run into trouble with "Web/Registration/{sessionKey}/Register". We create a valid {sessionKey} using "Web/Session" and populate the Registration body with the following test data:
OK. This was our error on our Staging environment - a custom trigger was attempting to use a DB Mail Profile that had been renamed...