Thanks Greg, provided I tell curl to write a cookie, with the -L option I'm now getting a good response, and if I then tell curl to use this cookie for subsequent commands I don't need to use the "-H "Authorization:Basic XXXXXXXXXXXXXXXX" option so I can get on with my automation - many thanks.  Matt
My issue is around getting authorization information.  "curl -k -X GET  [URL]" works fine, because it does not need any authorization  I then tried: curl -H "Accept:application/json" -H "Content-type:application/json" -H "X-EMC-REST-CLIENT:true" -H "Authorization:Basic XXXXXXXXXXXXXXXX" -k -X GET [URL]  Where XXXXXXXXXXXXXXXX is the Base64 encoding of "admin:myarraypassword"  I know that I need to get the EMC-CSRF-TOKEN/Ticket granting cookie but was expecting to get this with the first GET request I do - should I be using a different URL to do this initial authorization, or does any GET to a valid URL work?  I've seen perl and python examples, but as I am not familiar with either of these 2 languages, then this doesn't help me much.  The response I get is:   302 Found     The document has moved [URL]">here.      thanks  Matt 
How can I use curl to interact with the Unity REST API