Create a new initiative

post https://api.intelig.ai/api/v1/intelig/strategy/initiatives

Auth: Authorization: ApiKey <key> (an API key sent as Bearer is rejected) or Authorization: Bearer <jwt> for a dashboard session. operationId: createInitiative

Creates a strategic initiative with name, description, ownership scope, and optional timing details

Example request

curl -X POST "https://api.intelig.ai/api/v1/intelig/strategy/initiatives" \
  -H "Authorization: ApiKey $INTELIG_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "themeId": 1,
    "name": "Autonomous Intelligence",
    "description": "Run the execution loop, not just report on it",
    "successCriteria": "Link proposals confirmed without a human step",
    "ownerScopeType": "ORGANIZATION",
    "canonicalId": "INI-57",
    "targetQuarter": "Q2",
    "targetYear": 2026
  }'

Request body

application/json

Field	Type	Required	Description
`themeId`	integer (int64)	yes	ID of the theme to associate the initiative with Example: 42
`name`	string	yes	Initiative name (max 200 characters) Example: Mobile App v2
`description`	string	no	Detailed description of the initiative Example: Rebuild the mobile application with React Native
`successCriteria`	string	no	Criteria for measuring initiative success Example: 50% reduction in load time
`ownerScopeType`	string	yes	Who owns the initiative. ORGANIZATION is the normal case and takes a null ownerScopeId; TEAM and CONTRIBUTOR require ownerScopeId to identify which one. One of: ORGANIZATION, TEAM, CONTRIBUTOR Example: ORGANIZATION
`ownerScopeId`	integer (int64)	no	Id of the owning team or contributor. Null when ownerScopeType is ORGANIZATION.
`ownerName`	string	no	Display name of the owner Example: Platform Team
`startDate`	string	no	Initiative start date in ISO format Example: 2026-01-15
`endDate`	string	no	Initiative end date in ISO format Example: 2026-06-30
`targetQuarter`	string	no	Target quarter for delivery Example: Q2
`targetYear`	integer (int32)	no	Target year for delivery Example: 2026
`canonicalId`	string	no	Canonical initiative id used to attribute commits and PRs that reference it (e.g. a commit message ending in `(INI-57)`). Must be an `INI-<number>` spelling — `INI-57`, `INI_57` and `ini57` are all accepted and stored as `INI-57`. Unique per organization. Optional; an initiative without one simply cannot be referenced by id. Example: INI-57

Response 200

application/json · ApiResponseInitiativeDto

Field	Type	Description
`success`	boolean	—
`message`	string	—
`data`	InitiativeDto	Initiative details response

Status codes

200 — Initiative created successfully
400 — Invalid request body or validation failure
401 — Not authenticated
403 — Insufficient permissions to access strategy pillar
404 — Referenced theme not found
429 — —

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.