Skip to main content
POST
/
playbook
/
execution
/
batch
Execute concurrent investigations for multiple issues
curl --request POST \
  --url https://api.wildmoose.ai/playbook/execution/batch \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "inputList": [
    {
      "messageLink": "https://slack.com/archives/C1234567890/p1234567890123456"
    },
    {
      "title": "High memory usage detected",
      "time": "2025-01-15T10:30:00Z",
      "attributes": {
        "host": "web-server-01",
        "environment": "production"
      }
    },
    {
      "bookName": "perf-checks",
      "time": "2025-01-15T10:30:00Z"
    }
  ],
  "liveRun": false,
  "channelId": "C1234567890"
}
'
[
  {
    "highlights": "Root cause: Database connection pool exhaustion. The CPU spike correlates with increased database queries from the application layer. Immediate action: Scale database connection pool from 20 to 50 connections.",
    "gadgetsHighlights": [],
    "enrichmentLink": "https://slack.com/archives/C1234567890/p6543210987654321",
    "actionResults": [
      {
        "title": "Check system metrics",
        "shortAnswer": "CPU usage is at 85%",
        "mostImportantLink": "https://grafana.example.com/dashboard/cpu"
      }
    ]
  },
  {
    "error": "Failed to run playbook for alert High memory usage detected"
  }
]

Authorizations

​
Authorization
string
header
required

JWT token obtained from Auth0

Body

application/json
​
inputList
object[]
required

Array of playbook execution inputs (maximum 10 items)

Required array length: 1 - 10 elements

Playbook execution input. Either messageLink or time must be provided to specify when the issue occurred. If bookName is not provided, either messageLink or title must be specified to identify which playbook to run.

Example:
[
  {
    "messageLink": "https://slack.com/archives/C1234567890/p1234567890123456"
  },
  {
    "title": "High memory usage detected",
    "time": "2025-01-15T10:30:00Z",
    "attributes": { "host": "web-server-01" }
  }
]
​
liveRun
boolean
default:false

If true, sends enrichment results to the incident management tool for all executions

​
channelId
string

A Slack channel ID where results should be posted

Example:

"C1234567890"

Response

Batch playbook execution completed

​
error
string

Error message if the playbook execution failed

Example:

"Failed to execute playbook: timeout"

​
highlights
string

Bottom-line summary containing root cause analysis, conclusions, and key insights derived from the playbook execution

Example:

"Root cause: Database connection pool exhaustion. The CPU spike correlates with increased database queries from the application layer. Immediate action: Scale database connection pool from 20 to 50 connections."

​
gadgetsHighlights
object[]

Array of gadget highlight results

​
enrichmentLink
string

Link to the Slack message thread where enrichment results were posted (only present when channelId was specified)

Example:

"https://slack.com/archives/C1234567890/p6543210987654321"

​
actionableMitigations
object[]

Array of actionable mitigations

​
actionResults
object[]

Array of action execution results