Skip to content

Depot agentupdate

Registers the two routes beside the other endpoint actions, under the same permission.

This page is generated from the Depot route table. Every operation carries the permission it needs and the anchor an agent can link to.

POST /api/v1/endpoints/{agentID}/agent-update/check

Section titled “POST /api/v1/endpoints/{agentID}/agent-update/check”

POSTendpoint:actiontenant facehosteditmspremote

From an MSP console, prefix the path with /api/v1/clients/{clientID} to reach one client.

Source: [object Object]

dispatchAgentUpdate persists one agent_update Command and pushes it to the endpoint’s live stream.

The shape is dispatchEndpointAction’s, deliberately: the same TTL, the same pending-on-offline answer, and the command id as the idempotency key, so the console reads every endpoint action’s 202 alike.

NameInTypeRequiredDescription
agentIDpathstringYesA uuid.
StatusBodyDescription
202application/json, CommandAcceptedAccepted.
401application/problem+json, ProblemDetailsNo signed-in identity.
403application/problem+json, ProblemDetailsThe identity does not hold endpoint:action.
404application/problem+json, ProblemDetailsNo resource matches that id.
500application/problem+json, ProblemDetailsNo client context in request.
502application/problem+json, ProblemDetailsCould not dispatch command to agent.
503application/problem+json, ProblemDetailsThis Depot has no agent connection service, so nothing can be dispatched.

202 response body

FieldTypeDescription
commandIdrequiredstring
deliveredrequiredboolean
staterequiredstring
Terminal window
# Sign in first. outpost_console is a session cookie, so send it with every request.
curl -X POST 'https://depot.example.com/api/v1/endpoints/<agentID>/agent-update/check' \
-H 'X-CSRF-Token: <csrf-token>' \
-H 'Accept: application/json' \
-b 'outpost_console=<console-session>'

POST /api/v1/endpoints/{agentID}/agent-update/install

Section titled “POST /api/v1/endpoints/{agentID}/agent-update/install”

POSTendpoint:actiontenant facehosteditmspremote

From an MSP console, prefix the path with /api/v1/clients/{clientID} to reach one client.

Source: [object Object]

dispatchAgentUpdate persists one agent_update Command and pushes it to the endpoint’s live stream.

The shape is dispatchEndpointAction’s, deliberately: the same TTL, the same pending-on-offline answer, and the command id as the idempotency key, so the console reads every endpoint action’s 202 alike.

NameInTypeRequiredDescription
agentIDpathstringYesA uuid.
StatusBodyDescription
202application/json, CommandAcceptedAccepted.
401application/problem+json, ProblemDetailsNo signed-in identity.
403application/problem+json, ProblemDetailsThe identity does not hold endpoint:action.
404application/problem+json, ProblemDetailsNo resource matches that id.
500application/problem+json, ProblemDetailsNo client context in request.
502application/problem+json, ProblemDetailsCould not dispatch command to agent.
503application/problem+json, ProblemDetailsThis Depot has no agent connection service, so nothing can be dispatched.

202 response body

FieldTypeDescription
commandIdrequiredstring
deliveredrequiredboolean
staterequiredstring
Terminal window
# Sign in first. outpost_console is a session cookie, so send it with every request.
curl -X POST 'https://depot.example.com/api/v1/endpoints/<agentID>/agent-update/install' \
-H 'X-CSRF-Token: <csrf-token>' \
-H 'Accept: application/json' \
-b 'outpost_console=<console-session>'

Content is licensed CC BY 4.0. Code samples are MIT. Outpost and the Outpost mark are trademarks of Outpost Business Solutions, PBC and are not covered by either license.