Using Postman to create multiple Websites via API & CSV?

Is the pre-request script running each time you are making the call?

Personally this is something I would use Python or Powershell for. Loop through the items in the csv then call the API or SDK with that.

$headers.Add("X-Version",'3')

Can’t remember if it should be a string or not. Not a POSH guy anyway, so i don’t know if it matters even. 

To pass the version header, add this @Kelemvor :
$headers.Add("X-Version",'3')
 

Just under the other lines that are similar.

Otherwise, I have a working python script to add a website here: https://github.com/krshearman/LMAPI_v3/blob/main/PostAddWebsite.py

Hey there, 

I am by no means the most organized PowerShell person, but I have successfully gotten this working by reading a csv file for my website names. Additionally I have put the API credential and header work into a function and I call that when you see send-request.

CSV Example

google.com

amazon.com

$websites = Import-Csv -Path "PUT YOUR FILE PATH HERE" header name

$resourcePath = "/website/websites/"

$queryParams = ""

# Loop through each website and create a new website with the given request body

$i=0

foreach ($website in $websites){

    $data='{

        "type": "webcheck",

        "domain": "' + $websites[$i].name + '",

        "testLocation": {

            "smgIds": [2, 3, 4]

        },

        "name": "' + $websites[$i].name + '",

        "steps": [

            {

                "url": "' + $websites[$i].name + '",

                "timeout": 120

            }

        ]

    }'

    #Main Client Group

    #$data='{"type":"webcheck","domain":"' + $websites[$i].name + '","testLocation":{"smgIds":[2, 3, 4]},"name":"' + $websites[$i].name + '","steps":[{"url":"' + $websites[$i].name + '","timeout":120}]}'

    $results = Send-Request $resourcePath $httpVerb $queryParams $data

    write-host $data

    Write-Host $results

    $i = $i + 1

}

Also, for website groups I use this:

$CsvFilePath = "C:\Temp\SiteCodes.txt"

# Read the CSV file

$SiteCodes = Import-Csv -Path $CsvFilePath -header siteCode

$resourcePath = '/dashboard/groups/'

# Loop through the site codes and create dashboard groups

foreach ($SiteCode in $SiteCodes) {

    # Build the JSON request body

    $data = @{

        name = "$($SiteCode.siteCode) Dashboard Group"

    } | ConvertTo-Json

    # Send the API request to create the dashboard group

    $Response = send-request -resourcePath $resourcePath -httpVerb POST -data $data

    # Print the response to the console

    Write-Output "Dashboard group created: $($Response.name)"

}

Maybe this helps and maybe not but figured I would share what worked for me.

Hey there, just wanted to throw out a mention for the Logic.Monitor PS module. It is a wrapper for the LM API and works to make working with the API easier for admins use to interfacing with powershell. There are around ~150 cmdlets with more being added each week. Feel free to check it out as it will make light work of what you are attempting to do without having to learn python.

GitHub:

https://github.com/stevevillardi/Logic.Monitor

PS Gallery:

https://www.powershellgallery.com/packages/Logic.Monitor/

Intro post with some quick start info: 

I have no idea.  I don’t know Postman or Python very well, but I do know Powershell.  Although I’ve never used it for doing any API stuff.  Do you have a sample of using Powershell do hit the LM APIs by chance that I could use as a starting point?

Thanks.

This is dirty but should get the idea out there. This was a tab delimeted file not a csv but reading a csv is pretty simple.

$accessId = ''
$accessKey = ''

$ParentFolder = '5937'

$httpVerb = 'POST'
$resourcePath = '/device/groups'
$url = 'https://PORTAL.logicmonitor.com/santaba/rest' + $resourcePath

$Locations = Import-Csv C:\Users\user\Downloads\folders.txt -Delimiter "`t" -Header "SiteName","Street","City","State","Zip"

foreach ($Location in $Locations) {
    Write-Host $Location.SiteName
    $data = '{"name":"' + $Location.SiteName + '","parentId":' + $ParentFolder + ',"customProperties":[{"name":"location","value":"' + $Location.Street + ", " + $Location.City + ", " + $Location.State + " " + $Location.Zip + '"}]}'
    $epoch = [Math]::Round((New-TimeSpan -start (Get-Date -Date "1/1/1970") -end (Get-Date).ToUniversalTime()).TotalMilliseconds)
    <# Concatenate Request Details #>
    $requestVars = $httpVerb + $epoch + $data + $resourcePath

    <# Construct Signature #>
    $hmac = New-Object System.Security.Cryptography.HMACSHA256
    $hmac.Key = [Text.Encoding]::UTF8.GetBytes($accessKey)
    $signatureBytes = $hmac.ComputeHash([Text.Encoding]::UTF8.GetBytes($requestVars))
    $signatureHex = [System.BitConverter]::ToString($signatureBytes) -replace '-'
    $signature = [System.Convert]::ToBase64String([System.Text.Encoding]::UTF8.GetBytes($signatureHex.ToLower()))

    <# Construct Headers #>
    $auth = 'LMv1 ' + $accessId + ':' + $signature + ':' + $epoch
    $headers = New-Object "System.Collections.Generic.Dictionary[[String],[String]]"
    $headers.Add("Authorization",$auth)
    $headers.Add("Content-Type",'application/json')

    $response = Invoke-RestMethod -Uri $url -Method $httpVerb -Header $headers -Body $data
}

I’m not familiar with Postman at all myself but one thing about LM API calls is that you need to include any POST/PUT data into the sha256 algorithm that is used in the LMv1 auth header or it will fail. So need to make sure Postman is doing that when using the “Runner” section you talked about.

For PowerShell, there are some unofficial modules in PSGallery otherwise LM provides some examples at https://www.logicmonitor.com/support/rest-api-developers-guide/v1/rest-api-v1-examples#h-powershell-examples, just add the X-Version header to use APIv3 (v1 and v2 are going to be depreciated soon)

Ah thanks.  I’ll take a look.  I also found this page, but it says it’s from v1.  Hopefully it still works too.

https://www.logicmonitor.com/support/rest-api-developers-guide/v1/rest-api-v1-examples

The examples on that page and mine above will work with V3, the returned data structure is just different.