---
title: "Solve Rule"
method: POST
path: "/rule/solve/{ruleId}/{version}?"
---

# Solve Rule

`POST /rule/solve/{ruleId}/{version}?`

This endpoint allows you to solve your rule while providing input data in JSON format. If the `{version}` parameter is omitted from the path, the last published version will be used automatically.

## Path parameters

- `ruleId` string, required
- `version` integer

## Headers

- `Authorization` string, required
- `Content-Type` string
- `X-Strategy` 'STANDARD' | 'ARRAY' | 'FIRST_MATCH'
- `X-Correlation-Id` string
- `X-Audit` 'true' | 'false'
- `X-Audit-Ttl` string

## Request body

- object
  - `data` object — JSON object that describes the input json data.
  - `options` object — Object specifying solver options.

## Response `200`

OK

- object[]

## Other responses

- `400` — Bad Request
- `401` — Authentication token missing

---

[API](https://skmtc.dev/decisionrules/apis/decisionrules-rule-solver-api.md) · [All operations](https://skmtc.dev/decisionrules/apis/decisionrules-rule-solver-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/decisionrules/decisionrules-rule-solver-api/revisions/b50a7df65838/schema)