Invoke-WebRequest Bad Request using Rest API

[vine]

I'm trying to get the rawcontent using jira rest api using powershell.

(Invoke-WebRequest -credentials get-credential "https://name.jira.com/rest/api/2/search?jql=project%20%3D%20PPM%20AND%20status%20%3D%20%22Waiting%20Approval%22&fields=key").rawcontent

However, after running this script I get Bad Request even when I enter my credentials after getting prompted

Invoke-WebRequest : The remote server returned an error: (400) Bad Request.
At line:1 char:2
+ (Invoke-WebRequest -Credential get-credential "https://solutions.frae ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke
-WebRequest], WebException
+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWe
bRequestCommand


Has anyone encountered this before? The pretty sure the account I used is correct as I used it to login to jira but it doesn't work when I run this script. Main reason for creating this script is I want to get the output of the Issue Keys so I can use it as the parameters for the other script I used.

[Daniel Wester]

Due to the nature of JIRA - any JIRA admin can make a change only impact one project and but then another admin can make another change  such as adding all projects to the custom field the first added - it's kinda hard to track. Your best approaches are:

1. to limit the number of admins. 
2. Since you're using Cloud - have multiple Cloud instances.
3. Use an equal allocation of cost approach. (ie. you've got 25 admins – eek - that's 1/25 charge per admin).