Developers

Actions API

One POST per tool. Same validators as the desk and MCP. Org always comes from the verified token.

Call shape

Base

https://pm-api.cloudcrew.si/actions

Method

POST /actions/<name>

Auth

Bearer employee JWT or alk_ connector

bash
curl -sS -X POST 'https://pm-api.cloudcrew.si/actions/issue_get' \
  -H 'Authorization: Bearer <token>' \
  -H 'Content-Type: application/json' \
  -d '{"key":"CC-12"}'
Never send orgId from the client. Identity stamps the workspace. Approval-gated actions need the person’s OK header — don’t invent it.

Action families

FamilyExamples
Boardoverview, board, board_meta, board_issues, board_lane
Issuesissue_list, issue_get, issue_create, issue_update, comment_*, relation_*
Structureproject_*, milestone_create, cycle_*, initiative_*, team_*
Contextdoc_list, doc_get, doc_save, doc_history, doc_restore
Shiprelease_*, catalog_*
Gitrepo_*, github_*
Workflowstatus_*, automation_*, webhook_*, intake_*
Runmy_tasks, task_run, task_finish, focus
Insightsinsights (Elite)

Full machine schema: OpenAPI. Chat mounts the same names as pm_<action> when PM is hired.