Test Support Rule
POST/api/support/admin/rules/:rule/test
Dry-runs a rule against an existing ticket: reports whether the rule's conditions match the ticket right now and which actions would run. Nothing is changed, sent, or recorded. The rule's is_active flag is ignored — an inactive rule can be tested.
support:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Request body
ticket_id(integer, required) — the id of the ticket to evaluate against. Must exist.
Response fields
matches(boolean) — whether every condition holds for the ticket.would_run[](object[]) — the rule's actions in order, each withtype(string),value(mixed, nullable) andlabel(string, nullable — the action's display label). Empty when the rule does not match, or when anhourlyrule has already fired in this status epoch.already_applied(boolean) — only ever true for anhourlyrule: the rule has already fired on this ticket since its status last changed, so the scheduled sweep would skip it.
Authentication: Bearer token with the support:write scope, or an authenticated session, from a caller with an active support role who also holds the support admin role. No tenant context — this endpoint is central.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden
Response Headers
Not Found
Response Headers
Unprocessable Content
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.