Hi Folks -
For those of you evaluating our new V2 API's, PowerShell offers quite a bit of functionality for automated, scripted types of interactions. Not a great fit where a visual interface and human intervention is concerned, of course.
A few caveats to be aware of:
1 - PowerShell's Invoke-RestMethod cmdlet is not up to the task of replacing curl - alas. It's support for headers DOES NOT include
support for Content-Type and Authorization-Type arguments, at least in 3.0, so you'd likely have to define custom web client objects to
overcome this. Happy to hear of other's experiences here...
2 - Whereas our code samples will suggest a space following the ":" with JSON formats, in the -d or --data args for curl, this won't do (even
though it works just fine - sigh - in a normal command shell). Get rid of that space and you should be all set.
We PowerShell types are probably on the fringes of this community, but I'd love to hear from others on their experiences with this
nifty scripting language, as I'm sure there are some scenarios that could be well served by its use.
Happy coding and looking forward to reading your contributions!
A valid e-mail address. All e-mails from the system will be sent to this address. The e-mail address is not made public and will only be used if you wish to receive a new password or wish to receive certain news or notifications by e-mail.
This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.