Skip to main content
TroopyDocs
Open Troopy
Troopy

API reference / Support Agent

Check the layers of customers again

Asks for a re-check of the layers of the customers. Call it from your CI at the end of each deploy. Troopy reads the tools of your app as it lists them now, and checks each routine against them: its tool, the email argument and its other arguments. A tool that your app marks as read-only gets one call, and nothing goes to a chat. Then the active tests of the places run on your live product. A routine that broke shows its check in GET /support-liquid/layers, and the owners and admins hear of it. The asks of one deploy make one re-check, within about a minute. Not found while Liquid SaaS is off.

post/api/v1/support-liquid/recheck

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 recheck
MCP toolNone. Call it over REST or with the CLI.
Rate limit30 calls in 60 seconds, for each key
RetriesSend an Idempotency-Key header. A retry with the same key gets the first answer back, and the operation runs one time.

Body

application/json
reasonstring

What changed, like the version that you deployed

At most 120 characters

Response

202 · application/json
data*object
2 properties
queued*true
statusUrl*string

GET it after a minute: each routine has its check

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.
409 conflictThis Idempotency-Key was used for a different request, or that request is still running. Use a new key for a new request.
429 rate_limitedWait the number of seconds in Retry-After, then retry.