Skip to main content
TroopyDocs
Open Troopy
Troopy

API reference / Support Agent

Repair a routine of a customer whose tool went

Gives a broken routine the tool that the last re-check found in the place of the tool that went (check.fix of GET /support-liquid/layers). It is a new grant of an owner or admin for that tool, and the day that the grant ends stays. Troopy checks the tool again first, and never uses a tool that can write. A customer who heard of the break hears that it works again. POST /support-liquid/layers/{id}/undo takes it back for one minute. Not found while Liquid SaaS is off.

post/api/v1/support-liquid/layers/{id}/repair

Authorization

HeaderAuthorization: Bearer <API key>
Or the headerX-API-Key: <API key>
API keyMake one in Troopy under Settings > API keys. It acts as you, in its workspace.

Other ways to call it

CLItroopy liquid repair
MCP toolNone. Call it over REST or with the CLI.
Rate limit30 calls in 60 seconds, for each key

Path parameters

id*string

A 24-character id

Response

200 · application/json
data*object
2 properties
id*string

A 24-character id

tool*string

The tool that the routine calls now

Errors

400 invalid_inputFix the field named in detail. Each operation's schema is in /api/v1/openapi.json.
401 unauthorizedSend an API key as `Authorization: Bearer tr_live_...`. Create one in Troopy under Settings.
403 forbiddenThe key lacks a scope this operation needs, or its owner lacks the role. detail says which; create a key with the scope, or ask a company owner or admin.
404 not_foundCheck the path and any id in it. Every operation is listed in /api/v1/openapi.json.
429 rate_limitedWait the number of seconds in Retry-After, then retry.