Resolve API and versions

Your apps get answers from a decision with one HTTP request: send the input values, get the outputs of the first matching rule.

Every decision page shows a ready-to-copy request for that decision, with its id, its input keys and its current version filled in.

Secret keys

Requests are authorised with a secret key. Create one in Settings → Secret keys → Create secret key.

• Scope. A key for All projects resolves any decision in the workspace. A key for one project resolves only that project's decisions.
• Shown once. The key starts with sd_ and is shown only when you create it. SmartDecision stores only a hash of it, so copy it somewhere safe.
• Revoking. You can revoke the keys you created at any time, even while the workspace is read-only. When an admin removes a member, that member's keys stop working.

Use one key per integration, so a leaked key can be revoked without breaking the others.

Request

POST /api/resolve/{decisionId}

decisionId is the decision's number, shown in its sample request. Send the request to your SmartDecision server, for example http://decisions.internal:8080.

Headers

Body

Send one form field per input, named by the input's key, as application/x-www-form-urlencoded or multipart/form-data.

• Send every input of the decision, even inputs that the matching rule ignores. An empty value counts as missing.
• Send values as text in the input's format: 720, true, 2026-10-13. See Types.
• Fields that are not inputs of the decision are ignored.

curl -X POST http://decisions.internal:8080/api/resolve/42 \
  -H "Authorization: sd_your_secret_key" \
  -H "SmartDecision-Version: 1" \
  -d "credit_score=720" \
  -d "age=34"

const res = await fetch("http://decisions.internal:8080/api/resolve/42", {
  method: "POST",
  headers: {
    Authorization: "sd_your_secret_key",
    "SmartDecision-Version": "1",
  },
  body: new URLSearchParams({ credit_score: "720", age: "34" }),
});
const { output, rule } = await res.json();

Browsers can call the API from any origin. Keep secret keys on your servers, though: anyone who can read a key can resolve with it.

Response

When a rule matches, the status is 200 and the body holds its outputs and position:

{
  "output": { "decision": "approved" },
  "rule": { "position": "1" }
}

• output has one field per output key of the matching rule.
• Every value is a JSON string, numbers and true/false values included. Convert them in your code, for example "0.15" to a number.
• rule.position is the matching rule's position in the table, also as a string.

When no rule matches, the status is still 200, with a message and no outputs:

{ "message": "No rules matched" }

Check for output before you read it.

Response headers

Browsers can read all four headers.

Batch requests

To resolve many input sets against one decision in one request, for example to price a whole catalogue:

POST /api/resolve/{decisionId}/batch

The headers are the same. The body is JSON with an inputs array, 1 to 2000 sets per request and at most 2 MB. Every value must be a JSON string.

curl -X POST http://decisions.internal:8080/api/resolve/42/batch \
  -H "Authorization: sd_your_secret_key" \
  -H "SmartDecision-Version: 1" \
  -H "Content-Type: application/json" \
  -d '{"inputs": [
        {"credit_score": "720", "age": "34"},
        {"credit_score": "610", "age": "45"},
        {"credit_score": "680"}
      ]}'

The results come back in the same order. Each one looks like a single response body. A set that can't be resolved gets a message instead, and the rest of the batch still runs:

{
  "results": [
    { "output": { "decision": "approved" }, "rule": { "position": "1" } },
    { "output": { "decision": "rejected" }, "rule": { "position": "3" } },
    { "message": "Missing input value age" }
  ]
}

Errors

Error bodies are either a JSON string, like "Invalid Client Secret", or an object with a message field. Handle both.