Skip to content
Back to skills

Powershell Rest Api

BSecurity

Use when calling REST APIs from PowerShell.

  • 2 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 10, 2026
ai-agentsgoshellgitapisecurity

Works with

  • api

Security analysis

B88/100
  • criticalSends environment variables or credentials to an external URL

Pro shows the line behind each finding and how to fix it

Scanned September 10, 2026

npx -y skills add LoopyLuci/Skills --skill powershell-rest-api --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Powershell Rest Api?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Powershell Rest Api
[![Security: B — Skills Directory](https://www.skillsdirectory.com/api/skills/loopyluci-powershell-rest-api/badge)](https://www.skillsdirectory.com/skills/loopyluci-powershell-rest-api)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: powershell-rest-api
description: "Use when calling REST APIs from PowerShell."
category: software-development
tags: [powershell, rest, api, web, invoke-restmethod]
---
# PowerShell REST API

Calling REST APIs from PowerShell.

## Basic Requests

```powershell
# GET request
$response = Invoke-RestMethod -Uri "https://api.github.com/repos/user/repo"
$response.stargazers_count

# GET with headers
$headers = @{ Authorization = "Bearer $env:GITHUB_TOKEN" }
$response = Invoke-RestMethod -Uri "https://api.github.com/user" -Headers $headers

# POST with JSON body
$body = @{ name = "new-repo"; description = "Created via API" } | ConvertTo-Json
$response = Invoke-RestMethod -Uri "https://api.github.com/user/repos" `
    -Method Post -Headers $headers -Body $body -ContentType "application/json"
```

## Common Methods

```powershell
# PUT (update resource)
Invoke-RestMethod -Uri "https://api.example.com/items/1" `
    -Method Put -Body ($data | ConvertTo-Json) -ContentType "application/json"

# PATCH (partial update)
Invoke-RestMethod -Uri "https://api.example.com/items/1" `
    -Method Patch -Body '{"status": "active"}' -ContentType "application/json"

# DELETE
Invoke-RestMethod -Uri "https://api.example.com/items/1" -Method Delete -Headers $headers
```

## Authentication

```powershell
# Basic auth
$pair = "$($cred.UserName):$($cred.GetNetworkCredential().Password)"
$encoded = [Convert]::ToBase64String([Text.Encoding]::ASCII.GetBytes($pair))
$headers = @{ Authorization = "Basic $encoded" }

# Bearer token
$headers = @{ Authorization = "Bearer $token" }

# API Key
$headers = @{ "X-API-Key" = $apiKey }

# Cookie-based
$session = New-Object Microsoft.PowerShell.Commands.WebRequestSession
$cookie = New-Object System.Net.Cookie("session", $sessionId, "/", "example.com")
$session.Cookies.Add($cookie)
Invoke-RestMethod -Uri "https://example.com/api" -WebSession $session
```

## Error Handling

```powershell
try {
    $response = Invoke-RestMethod -Uri "https://api.example.com/data" -ErrorAction Stop
} catch [System.Net.WebException] {
    $statusCode = $_.Exception.Response.StatusCode
    $stream = $_.Exception.Response.GetResponseStream()
    $reader = New-Object System.IO.StreamReader($stream)
    $errorBody = $reader.ReadToEnd()
    Write-Error "HTTP $statusCode : $errorBody"
} catch {
    Write-Error "Request failed: $_"
}
```

## Pagination

```powershell
# GitHub-style pagination (Link header)
$uri = "https://api.github.com/user/repos?per_page=100"
$allRepos = @()
while ($uri) {
    $response = Invoke-WebRequest -Uri $uri -Headers $headers
    $repos = $response.Content | ConvertFrom-Json
    $allRepos += $repos
    # Parse Link header for next page
    if ($response.Headers.Link -match '<([^>]+)>;\s*rel="next"') {
        $uri = $matches[1]
    } else { $uri = $null }
}
```

## Polling Pattern

```powershell
do {
    $status = Invoke-RestMethod -Uri "https://api.example.com/jobs/$jobId"
    Write-Host "Status: $($status.state)"
    Start-Sleep -Seconds 5
} while ($status.state -eq 'running')

if ($status.state -eq 'completed') {
    Write-Host "Job completed: $($status.result)"
} else {
    Write-Error "Job failed: $($status.error)"
}
```

## Pitfalls

- Invoke-RestMethod returns parsed objects; Invoke-WebRequest returns raw HTTP response
- Default timeout is 100 seconds -- use `-TimeoutSec` for longer operations
- TLS 1.2 required for most modern APIs: `[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12`
- Proxy issues: `$env:HTTP_PROXY` or `-Proxy` parameter
- Rate limiting: check response headers for remaining quota

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.