You don't need that much parameters. You can test with postman.You need to do a post request to http[s]://<operator console>/rest/alarms/createAlarmAuthorization: Basic auth / username and password
But why don't you monitor the backup failure directly with logmon if the information is from a log file or from ntevl if the backup failure is written to a windows event viewer? Or let logmon execute a script that found the failure and open the alarm from logmon's script output.UIM is a monitoring tool, you should monitor the failure instead of manually found the failure and manually open an alarm.The solution of creating the alarm from the API call could work but you now need to monitor the return code of your api request in case it does not work or if the API was not available. At least, from logmon the alarm message goes to an alarm queue and will stay there until it get consume and transform as a real alarm. Messages that are not consumed yet are on disk inside the folder hub/q/<alarm queue> so you will not loose it.If you don't handle a retry from your api request in case of failure you will never know about your backup failure.