Hey thanks so much for putting this out here! Very instructive and helpful!

Updated sample scripts to adapt to changes in the JSON format, and to include an example of API Key support.

@Beau Alexander

Wow Erik, this is fantastic! Thank you so much for taking the time to give back to Community!

Since we're on the topic of PowerShell, I wanted to provide a cross-reference for you and any readers to make sure you knew about @Jose GALA's PowerShell cmdlet for Active Directory. It's in the Data Connections space, where we're building a space for everybody to talk about how they're sourcing their data.

In my company's version of the TBM Office, we don't use a lot of Python.  Probably should, and I'll put that on my list of skills to build... For those who are in the same boat as me and want to try to use the DataLink 4 API using PowerShell, I wrote up a segment of 'recipe ingredients' from my experimentation that will allow folks who are stuck & looking for a little push to get going again.

Thanks to @Dan Kelly for the encouragement and feedback.

Enjoy.

----- begin -----

<#
#
# Note, these are EXAMPLES of the way I chose to implement the API methods in PowerShell!
#
# This is based on the information found in the DataLink API guide found within the DataLink 4 web interface
# ... and a lot of web searches on various aspects of utilizing invoke-restmethod in PowerShell!
#
# This is not written in order to actually operate as a script. This is meant as a kind-of "hamburger helper"
# for those working through & testing the API to understand the process on their own
#
# That is to say, "Use at your own risk"
#
#>

$frontdoorURI = "https://frontdoor.apptio.com/service/nonuilogin"
$DLBaseURI = "https://dl-<YOURCOMPANYHERE>-manager.apptio.com/api/v1/resource/agent"

#create a header package for authentication
$authvals = @{ping_uname=$user;ping_pwd=$password} | convertto-json

#use invoke-restmethod to connect to Frontdoor. Return a session variable named "mysession" to be used to get the session token
$results = invoke-restmethod -uri $frontdoorURI -method post -body $authvals -contenttype 'application/json' -sessionvariable mysession

#retrieve the session token
$cookies = $mysession.Cookies.getCookies($frontdoorURI)
$token = @{$cookies.name = $cookies.value}

<#
#
# At this point, there should be a successful login, and the appropriate session token is in $token
#
# Now to take some action --
# - get AGENTS
# - get CONNECTORS
# - EXECUTE connector
#>

#get the AGENTS on the datalink instance. Returns high-level data for the agents in $agents
$agents = invoke-restmethod -uri $DLBaseURI -method get -headers $tokenComp

#get all the CONNECTORS on a specific AGENT -- note the GET method needs the '-headers' to include the session token. This returns data for all connectors on the Agent
$DLOperatingURI = $DLBaseURI + "/" + $agents.id + "/connector"
$connectors = invoke-restmethod -uri ($DLOperatingURI.id+"?include=name,type") -method get -headers $token

#EXECUTE a particular CONNECTOR on a specific agent
$DLConnectorURL = $DLOperatingURI + "/" + $someConnector.ConnectorID

#Now, create the command statement in JSON format
$task_exec = @{ "task" = "ExecuteConnector" } | convertto-json

#send the execute command here. Note the POST requires the token in '-headers', same as GET, and '-body' contains our task execution statement
$execConnector = invoke-restmethod -uri ($DLConnectorURL+"/execute") -method post -headers $token -body $task_exec -contenttype 'application/json'

----- end -----