Hey! Yeah, invoke webrequest can be tricky with some sites. A 403 usually means the server’s blocking you—maybe they’re checking for a user-agent or headers. Try adding a basic one like this:
```powershell
Invoke-WebRequest -Uri "https://example.com/api/data" -Headers @{"User-Agent"="Mozilla/5.0"}
```
Also, some sites hate PowerShell’s default UA. If it’s still failing, check if the site uses Cloudflare or something similar—they’re picky.
```powershell
Invoke-WebRequest -Uri "https://example.com/api/data" -Headers @{"User-Agent"="Mozilla/5.0"}
```
Also, some sites hate PowerShell’s default UA. If it’s still failing, check if the site uses Cloudflare or something similar—they’re picky.
