API Reference / Strategy - Initiative Link Proposals
Untracked candidates suggested for a given initiative
get
https://api.intelig.ai/api/v1/intelig/strategy/initiatives/link-proposals/by-initiative/{initiativeId}
Auth: Authorization: ApiKey <key> (an API key sent as
Bearer is rejected) or Authorization: Bearer <jwt>
for a dashboard session. operationId: byInitiative
The reverse view: work the matcher thinks belongs to this initiative but which is not attributed to it yet, ordered by confidence. This is the list to walk when automating approval — take the proposal ids from here and post each to the confirm endpoint. Requires the `strategy:read` scope.
Example request
curl -X GET "https://api.intelig.ai/api/v1/intelig/strategy/initiatives/link-proposals/by-initiative/1" \
-H "Authorization: ApiKey $INTELIG_API_KEY" Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
initiativeId | integer (int64) | yes | — |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
limit | integer (int32) | no | Max number of candidates |
Response 200
application/json · ApiResponseListInitiativeLinkProposalDto
| Field | Type | Description |
|---|---|---|
success | boolean | — |
message | string | — |
data | InitiativeLinkProposalDto[] | — |
Status codes
200— Candidates returned (ordered by confidence)401— Not authenticated403— Insufficient permissions to access strategy pillar429— —
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.