Playbooks in Scrubbe are versioned, executable runbooks that codify your team’s incident response procedures. You can create and publish playbooks through the API, match a playbook to a live incident context, and trigger executions that guide responders through each step — completing or skipping steps individually, recording ad-hoc actions, and cancelling when needed. Ezra AI can also suggest response actions based on real-time incident context, and the patterns endpoint surfaces lessons from historical executions.Documentation Index
Fetch the complete documentation index at: https://docs.scrubbe.com/llms.txt
Use this file to discover all available pages before exploring further.
All endpoints require
Authorization: Bearer <token>. Only published playbooks are eligible for matching and execution. Use POST /:id/publish to promote a draft.https://your-api-domain.com/api/v1/playbooks
Create a playbook
Creates a new playbook inDRAFT status. Publish it with POST /:id/publish when it is ready for use in incidents.
POST https://your-api-domain.com/api/v1/playbooks
Short title for the playbook (e.g.
"Database failover response").Overview of when this playbook should be used.
Ordered list of response steps.
Conditions used during automatic matching — service area, severity, environment, and similar fields.
Unique playbook identifier.
Initial status — always
DRAFT.ISO 8601 creation timestamp.
List playbooks
Returns a paginated list of playbooks ordered by creation date descending. Filter by status to view only published playbooks available for execution.GET https://your-api-domain.com/api/v1/playbooks
Page number.
Items per page (max 100).
Filter by status:
DRAFT or PUBLISHED.cURL
Get playbook stats
Returns aggregate statistics across all playbooks — total executions, average completion time, step skip rates, and most-executed playbooks.GET https://your-api-domain.com/api/v1/playbooks/stats
cURL
Total playbook count in the workspace.
Total number of executions across all playbooks.
Average time to complete an execution in minutes.
Proportion of optional steps skipped across all executions, from
0 to 1.Get a playbook
Fetch a single playbook by its ID, including its full step list and trigger conditions.GET https://your-api-domain.com/api/v1/playbooks/:id
The playbook ID.
cURL
Update a playbook
Update an existing playbook. Only the fields you provide are modified. Updating a published playbook creates a new draft version; usePOST /:id/publish to promote it.
PUT https://your-api-domain.com/api/v1/playbooks/:id
The playbook ID.
POST /.
Publish a playbook
Promote a draft playbook toPUBLISHED status, making it eligible for matching and execution.
POST https://your-api-domain.com/api/v1/playbooks/:id/publish
The playbook ID to publish.
cURL
Delete a playbook
Permanently delete a playbook and all its associated execution history.DELETE https://your-api-domain.com/api/v1/playbooks/:id
The playbook ID to delete.
Match a playbook to an incident
Find the best-matching published playbook for a given incident context. Scrubbe scores all published playbooks against the provided context and returns the top match.POST https://your-api-domain.com/api/v1/playbooks/match
ID of the active incident. Scrubbe reads its context automatically.
Service area to match against when not providing an incident ID.
Incident priority:
LOW, MEDIUM, HIGH, or CRITICAL.Target environment (e.g.
"production", "staging").cURL
ID of the best-matched playbook.
Playbook title.
Confidence score for the match, from
0 to 1.Execute a playbook
Start a new execution of a published playbook. Returns an execution ID that you use to track and drive progress through each step.POST https://your-api-domain.com/api/v1/playbooks/:id/execute
The playbook ID to execute.
Link this execution to an active incident.
Email address of the engineer leading the execution.
Unique identifier for this execution.
Execution status —
IN_PROGRESS on creation.List executions
Returns a paginated list of all playbook executions in the workspace.GET https://your-api-domain.com/api/v1/playbooks/executions/list
Page number.
Items per page (max 100).
Filter by execution status:
IN_PROGRESS, COMPLETED, or CANCELLED.cURL
Get an execution
Fetch a single execution by its ID, including current step progress and per-step status.GET https://your-api-domain.com/api/v1/playbooks/executions/:executionId
The execution ID.
cURL
Execution identifier.
ID of the playbook being executed.
Linked incident ID, if any.
Execution status:
IN_PROGRESS, COMPLETED, or CANCELLED.Zero-based index of the step currently in progress.
Per-step state.
ISO 8601 timestamp when execution began.
Complete a step
Mark a step in an active execution as completed and advance to the next step.POST https://your-api-domain.com/api/v1/playbooks/executions/:executionId/steps/:stepIndex/complete
The execution ID.
Zero-based index of the step to complete.
Optional notes from the responder about this step.
cURL
Skip a step
Skip an optional step in an active execution. Only steps defined with"optional": true can be skipped.
POST https://your-api-domain.com/api/v1/playbooks/executions/:executionId/steps/:stepIndex/skip
The execution ID.
Zero-based index of the step to skip.
Reason for skipping the step.
Skipping a required step returns a
400 error. Mark the step as optional in the playbook definition to allow skipping.cURL
Record an ad-hoc action
Record an unscripted action taken during an execution — useful for capturing steps not covered by the playbook or for audit purposes.POST https://your-api-domain.com/api/v1/playbooks/executions/:executionId/action
The execution ID.
Description of the action taken.
cURL
Complete an execution
Mark the entire execution asCOMPLETED once all required steps have been finished.
POST https://your-api-domain.com/api/v1/playbooks/executions/:executionId/complete
The execution ID.
cURL
Cancel an execution
Cancel an active execution. Cancelled executions are retained for audit purposes and excluded from completion rate statistics.POST https://your-api-domain.com/api/v1/playbooks/executions/:executionId/cancel
The execution ID.
Reason for cancelling the execution.
cURL
AI: suggest response actions
Ask Ezra AI to suggest ad-hoc response actions based on an incident context. Returns an ordered list of recommendations that responders can act on immediately or log viaPOST /executions/:executionId/action.
POST https://your-api-domain.com/api/v1/playbooks/suggest
ID of the active incident to generate suggestions for.
Ordered list of AI-recommended response actions.
Overall confidence score for the suggestion set, from
0 to 1.Get execution patterns
Returns patterns detected across playbook execution history — steps most frequently skipped, executions that correlated with faster resolution, and playbooks with the highest completion rates.GET https://your-api-domain.com/api/v1/playbooks/patterns
cURL
Array of detected execution patterns.