Skip to main content
POST
/
v1
/
remediation
/
{remediationId}
/
reject
Reject remediation
curl --request POST \
  --url https://api.example.com/v1/remediation/{remediationId}/reject \
  --header 'Content-Type: application/json' \
  --data '
{
  "reason": "<string>"
}
'

Documentation Index

Fetch the complete documentation index at: https://docs.causeflow.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Rejects a proposed remediation. Use this when you have reviewed the proposed steps and determined they are not appropriate — for example, if a safer alternative should be used instead. An optional reason can be provided to document why the remediation was rejected. This is useful for audit trails and for informing future AI suggestions. Required role: admin

​
Path parameters

​
remediationId
string
required
The unique identifier of the remediation to reject. Example: rem_01HX9VTPQR3KF8MZWBYD5N6JCE.

​
Request body

​
reason
string
Optional explanation for why this remediation was rejected. Providing a reason helps the AI refine future suggestions. Example: "This rollback would affect other tenants. Prefer the index creation approach instead."

​
Response

Returns 200 OK with the updated remediation status. 
{
  "remediationId": "rem_01HX9VTPQR3KF8MZWBYD5N6JCF",
  "status": "rejected"
}
FieldTypeDescription
remediationIdstringThe remediation that was rejected
statusstringAlways "rejected" after a successful call
Returns 404 Not Found if the remediation does not exist. Returns 403 Forbidden if the authenticated user is not an admin. Returns 409 Conflict if the remediation has already been approved, rejected, or executed.

​
Examples

curl https://api.causeflow.ai/v1/remediation/rem_01HX9VTPQR3KF8MZWBYD5N6JCF/reject \
  -X POST \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{"reason": "This rollback would affect other tenants. Prefer the index creation approach instead."}'