Developer portal
POST /tenant/scans/{scan_id}/remediation
Create or update remediation ownership, status, notes, and target date.
PilotPOST /tenant/scans/{scan_id}/remediationAuth: operator | admin
Summary
Create or update remediation ownership, status, notes, and target date.
Example
curl
curl -X POST "https://sparkling-vibrancy-production-1a7a.up.railway.app/tenant/scans/{scan_id}/remediation" \
-H "Authorization: Bearer 811f31d4-5b8e-4ed0-a7a2-8176e05eba63" \
-H "Content-Type: application/json" \
-d '{
"remediationId": "rem_001",
"status": "in_progress",
"owner": "alice@example.com"
}'Request body
| Field | Type | Required | Description |
|---|---|---|---|
| remediationId | string | Yes | Remediation backlog item id. |
| status | string | Yes | New remediation state. |
| owner | string | No | Assigned owner. |
| notes | string | No | Operator notes. |
| targetDate | string (ISO8601) | No | Desired completion date. |
| assetId | string | No | Related asset identifier. |
Response
| Field | Type | Required | Description |
|---|---|---|---|
| item | object | Yes | Saved remediation row. |
Errors
| Code | Meaning | Typical cause | Suggested fix |
|---|---|---|---|
| 401 | Unauthorized | Missing or invalid API key in Authorization, x-api-key, or query param. | Send Bearer <key> or x-api-key with a valid tenant token. |
| 403 | Forbidden | Valid key but insufficient role (viewer attempting write) or wrong admin key. | Use operator or admin role key; check RBAC matrix. |
| 404 | Not found | Scan, schedule, share link, or resource id does not exist or expired. | Verify id and tenant scope; share links expire per expiresHours. |
| 422 | Unprocessable entity | Invalid payload shape, unsupported scenario, or infeasible constraints. | Fix field errors in response detail; relax constraints and retry. |
| 429 | Too many requests | Per-key rate limit exceeded (default 300 requests per minute) or public endpoint limit. | Backoff with jitter; cache results; request higher limit for production. |
| 500 | Internal server error | Unexpected backend failure; includes requestId in response. | Retry with exponential backoff; contact support with requestId if persistent. |
| 503 | Service unavailable | Persistence disabled, auth DB unreachable, or admin API not configured. | Retry shortly; schedules require Postgres persistence enabled. |
See the full errors reference.
Found an issue? Report documentation feedback