Run a sandbox evaluation against saved rulesets and saved APIs.
Synchronously evaluate one or more saved APIs against a selected set of rulesets and return the violations inline. No persistence. Used by the Ruleset Test Sandbox UI (“Test ruleset” on the ruleset detail screen and the API Governance Tab).
Rulesets are selected via either ruleset_ids (explicit) or categories (executes every active ruleset whose categories intersect the input) — exactly one of the two. APIs are selected via api_ids (required). This endpoint takes references only — to evaluate an API definition submitted in the request (CI/CD file, UI draft), use POST /api/evaluations/sandbox/oas. Caps: 10 APIs, 20 resolved rulesets, 20 input categories, 1,000 issues per response.
Body
Sandbox evaluation request — saved resources only. Exactly one of ruleset_ids / categories must be provided (non-empty). To evaluate an API definition submitted in the request body, use POST /api/evaluations/sandbox/oas instead.
Response
Evaluation completed. The response may include a non-empty error string when the engine returned failures for some (ruleset, api) pairs while others succeeded; successful pairs' issues are still present in issues. An empty rulesets[] indicates no rulesets matched (category resolution returned none, or all matching rulesets had a different resource_type than the APIs).
Rulesets actually executed in this run. Single-ruleset callers see one entry; category-based callers see the resolved set. Each entry carries the ruleset's configured action and its per-ruleset severity counts. Empty array means no rulesets matched the request (category input with no intersection, or the only matches had a different resource_type than the APIs).