When AEWS URL is accessed via a browser, it prompts for credentails and once you provide appropriate authorized credentials, the AEWS URL can be used there after.
If the same is being attempted from tools like curl/Postman, the same credentials might need to be passed as part of a header. Below document provides couple of samples around the same.
Release : 12.0
Component : Workload Automation AE
You can use the --user option or the Authorization header which needs base64 encrypted string
curl -X GET https://myURL:9443/AEWS/job/test -k --user "ejmadmin:ejmadmin"
curl -X GET https://myURL:9443/AEWS/job/test -k -H "Authorization: Basic ZWptYWRtaW46ZWptYWRtaW4=" -i
#note: The Authorization token above is ejmadmin:ejmadmin (which are the default credentials to login to AEWS)
The encrypted string can be obtained in a few ways:
1) echo -n "ejmadmin:ejmadmin" | base64
PS C:\Users\Administrator> $auth = [System.Text.Encoding]::UTF8.GetBytes("ejmadmin:ejmadmin")
PS C:\Users\Administrator> [System.Convert]::ToBase64String($auth)
3) Postman itself has the option to encrypt the credentials and create the Authorization header, you could also try to encrypt/depcrypt using websites https://www.base64decode.org