PowerShell循环调用Invoke-RestMethod无法获取响应内容的问题求助

Let's break down why you're seeing empty responses in your loop and how to fix it—this is definitely not expected behavior, so let's get to the bottom of it.

First, Rule Out Display Issues (Most Likely Culprit) #

The biggest reason for this confusion is that Write-Host doesn't handle complex objects well. When you output an object directly with Write-Host, it only shows the result of the object's ToString() method, which can be empty for nested JSON structures or arrays.

Try these adjustments to see the actual response content:

• Verify your team ID is correctly populated first:

  Write-Host "Fetching data for team ID: $($team.id)"
  

• Convert the response to JSON to view its full structure:

  Write-Host ($response | ConvertTo-Json -Depth 10)
  

• Use Format-List to display all properties of the response object:

  Write-Host ($response | Format-List * | Out-String)
  

Chances are, the $response variable has data—Write-Host was just hiding it.

If the Response Is Truly Empty #

If the above still shows nothing, bypass Invoke-RestMethod's automatic parsing and handle the raw response manually with Invoke-WebRequest:

foreach ($team in $teams) {
    Write-Host "Processing team ID: $($team.id)"
    
    # Get raw web response
    $webResponse = Invoke-WebRequest -Uri https://theUri/$($team.id) -Headers $header -Method Get
    
    # Confirm content was returned
    Write-Host "Raw content length: $($webResponse.Content.Length)"
    
    # Manually parse JSON
    $response = $webResponse.Content | ConvertFrom-Json
    
    # Display parsed data
    Write-Host ($response | ConvertTo-Json -Depth 10)
}

Invoke-RestMethod can fail silently in edge cases (like non-standard Content-Type headers), so handling raw content directly isolates parsing issues.

Upgrade PowerShell to Fix Known Bugs #

You're using PowerShell 7.1.3, a 2021 release with known bugs related to Invoke-RestMethod in loops (connection pooling, response parsing quirks). Upgrading to the latest stable version (7.3+) will likely resolve the issue entirely.

Verify API Response Consistency #

Even with 200 status codes, some team IDs might return empty bodies. Test the single-line script for each ID in $teams individually to confirm every endpoint returns non-empty data.

Ditch the Workaround #

Your current file-writing workaround works but is unnecessary once you fix the core issue. The steps above let you keep everything in a single, clean script.

内容的提问来源于stack exchange，提问作者Kevin Evans