How do I use invoke-webrequest with basic authentication header in PowerShell? or What's the correct

"Having trouble with invoke-webrequest with basic authentication header—any tips?"

Hey folks,

So I'm trying to use invoke-webrequest with basic authentication header, but it's being a pain. I keep getting 401 errors, and I *know* my creds are right.

I’ve tried stuff like:
```powershell
$headers = @{ Authorization = "Basic " + [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes("user:pass")) }
Invoke-WebRequest -Uri "https://example.com" -Headers $headers
```
But no luck. Am I missing something obvious?

Also, is there a cleaner way to do this? Feels like I’m overcomplicating it.

Thanks in advance!

(PS: If you’ve got a step-by-step breakdown, even better. My brain’s fried.)

Hey! I had the same issue last week. Turns out, some APIs are picky about trailing slashes in the URL. Try removing or adding one to your URI.

Also, double-check if the API expects the auth header in a different format. Sometimes it's "Bearer" instead of "Basic."

For a cleaner way, you could use `-Credential` with `Get-Credential` instead of manually encoding:
```powershell
$cred = Get-Credential
Invoke-WebRequest -Uri "https://example.com" -Credential $cred
```
Might save you some headaches!

Ugh, 401s are the worst. Have you tried using `-UseBasicParsing`? Some older systems freak out without it.

Also, maybe your creds have special chars? PowerShell can be weird with those. Try wrapping them in single quotes or escaping them.

If you're still stuck, Postman is a lifesaver for testing APIs before coding. Helps rule out if it's your script or the server.

Yo, random thought—are you sure the server even accepts basic auth? Some APIs force OAuth or tokens now. Check the docs!

If it *is* basic auth, your code looks right. Maybe the server’s case-sensitive with the header key? Try "authorization" lowercase.

Also, Fiddler or Wireshark can help see the raw request. Sometimes the issue isn’t even on your end.

Here’s a step-by-step that worked for me:

1. Encode creds like you did, but store them in a var first:
```powershell
$auth = "user:pass"
$encoded = [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes($auth))
```

2. Then, use `-Headers` *and* `-ContentType "application/json"` (if applicable).

3. Run `$Error[0] | fl -Force` after the error to get deets.

Sometimes the server’s error message hides in there.

Wild guess: Is your password super long? Base64 has limits, and some servers truncate it. Try a shorter test password.

Also, `Invoke-RestMethod` might behave better than invoke-webrequest with basic authentication header. Worth a shot!

If all else fails, curl in PowerShell (yes, it’s a thing now):
```powershell
curl -u user:pass https://example.com
```
Way less fuss.

Pro tip: Skip the manual header and use `-Authentication Basic` with `-Credential`. Works like a charm:
```powershell
$cred = New-Object pscredential -ArgumentList "user", (ConvertTo-SecureString "pass" -AsPlainText -Force)
Invoke-WebRequest -Uri "https://example.com" -Authentication Basic -Credential $cred
```

Also, check if the server’s expecting a `-Method POST`. GET by default might not cut it.

OP here—huge thanks to everyone! The `-Authentication Basic` flag was the magic fix. No idea why I missed that in the docs.

Still weird that the manual header didn’t work, but hey, it’s running now.

Side note: Tried Postman like someone suggested, and yeah, it confirmed the server’s fussy about casing. Learned my lesson!

Thanks again, y’all saved my sanity.