Skip to main content
TroopyDocs
Open Troopy
Troopy

API reference / Support Agent

See what a routine of a customer gives

Calls the tool of a routine one time with the key of the app and the email of the customer, runs its function, and gives the result back. Nothing goes to a chat. Use it before a grant. Only for a tool that the app itself marks as read-only: for each other tool, sample and problem are null, because Troopy never tries a write. When the tool or the function fails, problem says why. Needs an owner or admin. Not found while Liquid SaaS is off.

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

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 preview
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
3 properties
id*string

A 24-character id

sample*string | null

The words or the card that the customer gets. Null for a tool that can write, or with a problem

problem*string | null

Why a tool that reads gave no sample, such as a tool that went or a function that failed

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.