> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rootly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Deletes an AI automation

> Requires OAuth scope `ai.automations:write`. Retires the automation: it is disabled and soft-deleted, no longer listed or runnable; GET show and run-now return 404, while its existing run history remains readable via the runs endpoints.



## OpenAPI

````yaml https://rootly-heroku.s3.amazonaws.com/swagger/v1/swagger.json delete /v1/ai/automations/{id}
openapi: 3.0.1
info:
  title: Rootly API v1
  version: v1
  license:
    name: Rootly
    url: https://rootly.com
  description: >+
    # How to generate an API Key?

    - **Organization dropdown** > **Organization Settings** > **API Keys**


    # JSON:API Specification

    Rootly is using **JSON:API** (https://jsonapi.org) specification:

    - JSON:API is a specification for how a client should request that resources
    be fetched or modified, and how a server should respond to those requests.

    - JSON:API is designed to minimize both the number of requests and the
    amount of data transmitted between clients and servers. This efficiency is
    achieved without compromising readability, flexibility, or discoverability.

    - JSON:API requires use of the JSON:API media type
    (**application/vnd.api+json**) for exchanging data.


    # Authentication and Requests

    We use standard HTTP Authentication over HTTPS to authorize your requests.

    ```
      curl --request GET \
    --header 'Content-Type: application/vnd.api+json' \

    --header 'Authorization: Bearer YOUR-TOKEN' \

    --url https://api.rootly.com/v1/incidents

    ```


    <br/>


    # Rate limiting

    - There is a default limit of **5** **GET**, **HEAD**, and **OPTIONS** calls
    **per API key** every **60 seconds** (0 hours). The limit is calculated over
    a **0-hour sliding window** looking back from the current time. While the
    limit can be configured to support higher thresholds, you must first contact
    your **Rootly Customer Success Manager** to make any adjustments.

    - There is a default limit of **3** **POST**, **PUT**, **PATCH** or
    **DELETE** calls **per API key** every **60 seconds** (0 hours). The limit
    is calculated over a **0-hour sliding window** looking back from the current
    time. While the limit can be configured to support higher thresholds, you
    must first contact your **Rootly Customer Success Manager** to make any
    adjustments.

    - When rate limits are exceeded, the API will return a **429 Too Many
    Requests** HTTP status code with the response: `{"error": "Rate limit
    exceeded. Try again later."}`

    - **X-RateLimit headers** are included in every API response, providing
    real-time rate limit information:
      - **X-RateLimit-Limit** - The maximum number of requests permitted and the time window (e.g., "1000, 1000;window=3600" for 1000 requests per hour)
      - **X-RateLimit-Remaining** - The number of requests remaining in the current rate limit window
      - **X-RateLimit-Used** - The number of requests already made in the current window
      - **X-RateLimit-Reset** - The time at which the current rate limit window resets, in UTC epoch seconds

    # Pagination

    - Pagination is supported for all endpoints that return a collection of
    items.

    - Pagination is controlled by the **page** query parameter


    ## Example

    ```
      curl --request GET \
    --header 'Content-Type: application/vnd.api+json' \

    --header 'Authorization: Bearer YOUR-TOKEN' \

    --url https://api.rootly.com/v1/incidents?page[number]=1&page[size]=10

    ```

  x-logo:
    url: https://rootly-heroku.s3.us-east-1.amazonaws.com/swagger/v1/logo.png
servers:
  - url: https://api.rootly.com
security: []
paths:
  /v1/ai/automations/{id}:
    parameters:
      - name: id
        in: path
        schema:
          type: string
          format: uuid
        required: true
    delete:
      tags:
        - AIAutomations
      summary: Deletes an AI automation
      description: >-
        Requires OAuth scope `ai.automations:write`. Retires the automation: it
        is disabled and soft-deleted, no longer listed or runnable; GET show and
        run-now return 404, while its existing run history remains readable via
        the runs endpoints.
      operationId: DeleteAIAutomation
      responses:
        '200':
          description: write OAuth scope permits deleting automations
          content:
            application/vnd.api+json:
              schema:
                $ref: '#/components/schemas/ai_automation'
        '404':
          description: read OAuth scope cannot delete automations
          content:
            application/vnd.api+json:
              schema:
                $ref: '#/components/schemas/errors_list'
      security:
        - bearer_auth: []
components:
  schemas:
    ai_automation:
      type: object
      properties:
        data:
          type: object
          properties:
            id:
              type: string
              format: uuid
            type:
              type: string
              enum:
                - ai_automations
            attributes:
              type: object
              allOf:
                - $ref: '#/components/schemas/ai_automation_attributes'
          required:
            - id
            - type
            - attributes
      required:
        - data
    errors_list:
      type: object
      properties:
        errors:
          type: array
          items:
            type: object
            properties:
              title:
                type: string
              status:
                type: string
              code:
                type: string
                nullable: true
              detail:
                type: string
                nullable: true
            required:
              - title
              - status
    ai_automation_attributes:
      type: object
      properties:
        name:
          type: string
        prompt:
          type: string
        enabled:
          type: boolean
        trigger_kind:
          type: string
          enum:
            - schedule
            - event
          description: >-
            Legacy single-trigger view; not authoritative when the automation
            has more than one trigger. Read triggers for the full state.
        schedule:
          type: object
          nullable: true
          properties:
            frequency:
              type: string
              enum:
                - hourly
                - daily
                - weekdays
                - weekly
            hour:
              type: integer
              nullable: true
              minimum: 0
              maximum: 23
              description: Not used for hourly schedules.
            weekday:
              type: string
              nullable: true
              enum:
                - MO
                - TU
                - WE
                - TH
                - FR
                - SA
                - SU
              description: Only used for weekly schedules.
        schedule_rrule:
          type: string
          nullable: true
          description: >-
            Legacy single-schedule view; null unless the automation has exactly
            one schedule trigger. Custom RRULE. Can't be combined with
            schedule.frequency, schedule.hour or schedule.weekday;
            schedule.timezone is allowed.
        schedule_timezone:
          type: string
          nullable: true
          description: >-
            Legacy single-schedule view; null unless the automation has exactly
            one schedule trigger.
        event_name:
          type: string
          nullable: true
          enum:
            - incident.created
            - incident.updated
            - incident.status_changed
            - incident.severity_changed
            - incident.resolved
            - incident.cancelled
            - alert.created
            - alert.acknowledged
            - alert.resolved
            - slack.message_posted
            - slack.reaction_added
            - slack.usergroup_mentioned
            - webhook.received
          description: >-
            Legacy single-event view. null when the automation has no event
            trigger, more than one event, or alert, Slack or webhook conditions;
            read triggers instead.
        conditions:
          type: object
          description: >-
            Legacy view of incident trigger conditions. {} when event_name is
            null. Empty object means no conditions. Groups in any are ORed;
            clauses in all are ANDed.
          example:
            any:
              - all:
                  - field: status
                    operator: eq
                    value: started
          properties:
            any:
              type: array
              items:
                type: object
                properties:
                  all:
                    type: array
                    items:
                      type: object
                      properties:
                        field:
                          type: string
                          enum:
                            - severity
                            - status
                            - to_status
                        operator:
                          type: string
                          enum:
                            - eq
                            - neq
                            - contains
                            - present
                            - blank
                        value:
                          oneOf:
                            - type: string
                            - type: number
                            - type: boolean
                          description: Omitted for present/blank operators.
                      required:
                        - field
                        - operator
                      additionalProperties: false
                required:
                  - all
                additionalProperties: false
          additionalProperties: false
        triggers:
          type: array
          items:
            type: object
            properties:
              id:
                type: string
              source:
                type: string
                enum:
                  - schedule
                  - incident
                  - alert
                  - slack
                  - webhook
              event_name:
                type: string
                nullable: true
                enum:
                  - incident.created
                  - incident.updated
                  - incident.status_changed
                  - incident.severity_changed
                  - incident.resolved
                  - incident.cancelled
                  - alert.created
                  - alert.acknowledged
                  - alert.resolved
                  - slack.message_posted
                  - slack.reaction_added
                  - slack.usergroup_mentioned
                  - webhook.received
                  - null
              schedule_rrule:
                type: string
                nullable: true
              schedule_timezone:
                type: string
                nullable: true
              next_run_at:
                type: string
                format: date-time
                nullable: true
              cooldown_seconds:
                type: integer
              webhook_url:
                type: string
                description: >-
                  Webhook triggers only. POST JSON here with the secret in the
                  X-Webhook-Secret header.
              webhook_secret_configured:
                type: boolean
                description: >-
                  Webhook triggers only. The secret itself is never returned;
                  generate one with POST
                  /v1/ai/automations/{id}/triggers/{trigger_id}/webhook_secret.
              webhook_secret_rotated_at:
                type: string
                format: date-time
                nullable: true
                description: Webhook triggers only.
              conditions:
                type: array
                description: >-
                  All conditions on a trigger must match. Alert and webhook
                  payload conditions use the field token and JSONPath key
                  accepted on write.
                items:
                  type: object
                  properties:
                    field:
                      type: string
                    key:
                      type: string
                      nullable: true
                    field_type:
                      type: string
                    operator:
                      type: string
                    values:
                      type: array
                      items:
                        type: string
                  required:
                    - field
                    - field_type
                    - operator
                    - values
            required:
              - id
              - source
              - event_name
              - schedule_rrule
              - schedule_timezone
              - next_run_at
              - cooldown_seconds
              - conditions
        destination_kind:
          type: string
          enum:
            - slack_channel
            - incident_timeline
            - none
        destination_slack_target:
          type: string
          enum:
            - channel
            - trigger_thread
            - incident_channel
        destination_slack_channel_id:
          type: string
          nullable: true
        destination_slack_channel_name:
          type: string
          nullable: true
        skill_ids:
          type: array
          items:
            type: string
            format: uuid
        allowed_tool_keys:
          type: array
          nullable: true
          minItems: 1
          maxItems: 500
          items:
            type: string
          description: >-
            Tool keys are stable identifiers; connector tools use
            mcp:<lineage_root_id>:<tool_name> or
            private_connect:<agent_id>:<provider_id>:<capability>. null inherits
            all tools allowed by the team; otherwise the automation can use only
            these tool keys.
        limits_enabled:
          type: boolean
          description: >-
            Stored limit values are returned even when false and apply only when
            this is true.
        max_credits_per_run:
          type: number
          nullable: true
          description: >-
            The stored value is returned even when limits are disabled and only
            applies when limits_enabled is true.
        rate_limit_runs:
          type: integer
          description: >-
            The stored value is returned even when limits are disabled and only
            applies when limits_enabled is true.
        rate_limit_window:
          type: string
          enum:
            - 1_hour
            - 1_day
            - 7_days
          description: >-
            The stored value is returned even when limits are disabled and only
            applies when limits_enabled is true.
        owner_user_id:
          type: integer
          nullable: true
        disabled_reason:
          type: string
          nullable: true
        next_run_at:
          type: string
          format: date-time
          nullable: true
        last_run_at:
          type: string
          format: date-time
          nullable: true
        consecutive_failures_count:
          type: integer
        created_by_user_id:
          type: integer
          nullable: true
        created_at:
          type: string
          format: date-time
        updated_at:
          type: string
          format: date-time
  securitySchemes:
    bearer_auth:
      type: http
      scheme: bearer

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.