API Reference / Strategy - Initiative Link Proposals
Dismiss a proposal (soft delete — stays in audit)
delete
https://api.intelig.ai/api/v1/intelig/strategy/initiatives/link-proposals/{proposalId}
Auth: Authorization: ApiKey <key> (an API key sent as
Bearer is rejected) or Authorization: Bearer <jwt>
for a dashboard session. operationId: dismiss
Rejects the proposal. It stops appearing in the reads but is kept, because confirm/dismiss decisions are the labels the monthly link calibration learns from — dismissing is a signal, not a delete. Requires the `strategy:write` scope.
Example request
curl -X DELETE "https://api.intelig.ai/api/v1/intelig/strategy/initiatives/link-proposals/1" \
-H "Authorization: ApiKey $INTELIG_API_KEY" Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
proposalId | integer (int64) | yes | — |
Response 200
application/json · ApiResponseVoid
| Field | Type | Description |
|---|---|---|
success | boolean | — |
message | string | — |
data | object | — |
Status codes
200— Dismissed401— Not authenticated403— Insufficient permissions to access strategy pillar404— Proposal not found in this org429— —
Every response is wrapped in { success, message, data }. A 4xx means the request
is wrong — do not retry it unchanged. A 429 carries Retry-After in seconds.