curl --request POST \
--url https://api.wildmoose.ai/playbook/execution \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"messageLink": "https://slack.com/archives/C1234567890/p1234567890123456",
"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": [
{
"path": [
"body",
"messageLink"
],
"message": "Required"
}
]
}{
"error": "Internal server error"
}{
"error": "Client ID not configured for organization"
}{
"error": "Internal server error"
}Execute a playbook
Executes a playbook for a single point in time when a production issue took place. The request can either provide a message link to a Slack message describing the issue, or provide its details directly. Alternatively, if bookName is specified, the playbook is identified by name and messageLink/title are optional.
curl --request POST \
--url https://api.wildmoose.ai/playbook/execution \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"messageLink": "https://slack.com/archives/C1234567890/p1234567890123456",
"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": [
{
"path": [
"body",
"messageLink"
],
"message": "Required"
}
]
}{
"error": "Internal server error"
}{
"error": "Client ID not configured for organization"
}{
"error": "Internal server error"
}Authorizations
JWT token obtained from Auth0
Body
- Option 1
- Option 2
- Option 3
- Option 4
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.
Name of the playbook to run.
"perf-checks"
If true, sends enrichment results to the incident management tool
A Slack channel ID where results should be posted
"C1234567890"
The time when the issue occurred (ISO 8601 datetime). Optional, defaults to now.
"2025-01-15T10:30:00Z"
Response
Playbook execution completed successfully
Error message if the playbook execution failed
"Failed to execute playbook: timeout"
Bottom-line summary containing root cause analysis, conclusions, and key insights derived from the playbook execution
"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."
Array of gadget highlight results
Show child attributes
Show child attributes
Link to the Slack message thread where enrichment results were posted (only present when channelId was specified)
"https://slack.com/archives/C1234567890/p6543210987654321"
Array of actionable mitigations
Show child attributes
Show child attributes
Array of action execution results
Show child attributes
Show child attributes