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

# Delete Rule

> Delete a Customer Value rule by its ID. To stop a rule from firing without losing its configuration, update it with `status` set to `inactive` instead.


Deletes a Customer Value rule and its goals by its ID.

Deletion is permanent — the rule's goals go with it. To stop a rule from firing while keeping its configuration, [update](/api-reference/put-networksusmrules) it with `status` set to `inactive` instead.

Payout and revenue adjustments the rule already applied to past conversions are not reverted.


## OpenAPI

````yaml openapi/customer-value.yaml delete /networks/usm/rules/{ruleId}
openapi: 3.0.3
info:
  title: Everflow Network API - Customer Value
  description: >
    Endpoints for managing Customer Value — data points and rules — in the
    Everflow network.


    Customer Value was previously called **User Management**, and the API paths
    keep the `usm` prefix from that name.


    A **data point** declares a named customer attribute (`ltv_90d`,
    `plan_tier`) that you send in with conversions. A **rule** watches those
    data points, plus standard conversion metrics, and adjusts payout or revenue
    when a customer's aggregated values meet its goals. For setup, see [Customer
    Value](https://helpdesk.everflow.io/customer/customer-value) in the Help
    Center.
  version: 1.0.0
servers:
  - description: Production Server
    url: https://api.eflow.team/v1
security: []
tags:
  - name: Customer Value
    description: >-
      Data points and rules that drive Customer Value payout and revenue
      adjustments.
  - name: Reporting
    description: Conversion reporting scoped to a single customer.
paths:
  /networks/usm/rules/{ruleId}:
    delete:
      tags:
        - Customer Value
      summary: Delete Rule
      description: >
        Delete a Customer Value rule by its ID. To stop a rule from firing
        without losing its configuration, update it with `status` set to
        `inactive` instead.
      parameters:
        - in: path
          name: ruleId
          required: true
          schema:
            type: integer
          description: The rule identifier.
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  result:
                    type: boolean
      security:
        - API Key: []
components:
  securitySchemes:
    API Key:
      description: The Everflow API key generated from the Control Center > Security.
      in: header
      name: X-Eflow-Api-Key
      type: apiKey

````