Report your own step-up for a held API call

POST /api/v1/api-calls/decisions/{decisionId}/step-up · operationId stepUpApiCall

For developers: your server sends this request with a server key; it is not a button in the dashboard. To see the same information without code, open Control › Approvals › Waiting in the dashboard.

passed approves the held call for one use within 15 minutes (the next decide with approvedDecisionId); failed rejects it. Evidence your check succeeded, not authorization.

#Authentication

Send Authorization: Bearer YOUR_SERVER_KEY (siteServerKey: Site server key in Authorization: Bearer <key> (the scheme is case-insensitive and required; a bare key is 401). Shown once on creation or rotation. Publishable keys cannot authenticate). Keep the server key in server-only configuration; never send it to a browser.

#Parameters

• decisionId (path, string, required)

#Request body

Content-Type: application/json (required)

• result ("passed" | "failed", required)
• method ("passkey" | "mfa" | "turnstile" | "own_approval" | "other", optional)

{
  "result": "passed",
  "method": "passkey"
}

#Responses

• 200: Success · body object
• 400: bad_request: the request is invalid; message says what to fix and field names the request field · body Error
• 401: unauthorized (missing or invalid server key, missing Bearer scheme) · body Error
• 403: forbidden: the call came from a browser page or another Site; call from your server with this Site’s server key · body Error
• 404: not_found: unknown path, or an ID in the path that is not on this Site · body Error
• 409: conflict: the decision is not held, was already settled or has expired · body Error
• 413: payload_too_large: the request body exceeds 131072 bytes · body Error
• 429: rate_limited: wait for Retry-After · body Error · headers Retry-After
• 500: internal_error: fail the protected action; do not retry automatically · body Error
• 503: service_unavailable: temporarily unavailable; only verify retries · body Error

#Success body fields

• decisionId (string, required)
• status ("approved" | "rejected", required)
• expiresAt (integer | null, required)

Failures are not verdicts. Error bodies follow the Error schema: code is one of bad_request, unauthorized, session_reinit_required, forbidden, not_found, conflict, identity_required, payload_too_large, rate_limited, internal_error, service_unavailable, request_failed, approval_invalid, approval_used, approval_expired, approval_mismatch, step_up_not_held, step_up_mismatch, step_up_settled, step_up_expired, step_up_superseded, agent_tokens_disabled, tool_not_approved, tool_not_read_only. Errors and retries explains each code and what to do.

#Example

curl -sS -X POST 'https://app.trytelltale.dev/api/v1/api-calls/decisions/decision_PASTE_DECISION_ID/step-up' \
  -H "Authorization: Bearer $TELLTALE_SERVER_KEY" \
  -H 'Content-Type: application/json' \
  --data '{"result":"passed","method":"passkey"}'

const response = await fetch("https://app.trytelltale.dev/api/v1/api-calls/decisions/decision_PASTE_DECISION_ID/step-up", {
  method: "POST",
  headers: {
    Authorization: 'Bearer ' + process.env.TELLTALE_SERVER_KEY,
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    "result": "passed",
    "method": "passkey"
  }),
  signal: AbortSignal.timeout(5000)
});
const result = await response.json();

Machine-readable contract: openapi.json. Request builder: the API explorer shows every operation as curl; it sends requests only on a local dashboard.