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

# 删除 Notification Endpoint

<Warning>
  此页面由 AI 自动翻译。API 技术规格以英文呈现为标准。如有任何疑问，请参阅[英文版本](/api-reference/notification/delete-notification-endpoint)。
</Warning>

根据 [列出 Notification Endpoints](/zh-Hans/api-reference/notification/list-notification-endpoints) 返回的 `apiNotificationId` 删除一个已注册的通知端点。每次调用只能删除一个端点。响应不含 Payload——请读取 `meta.status` 以确认结果。

<Warning>
  删除是永久性操作。系统不提供停用或暂停功能；若要先停止、日后再恢复接收通知，请删除该端点并在日后重新注册，届时会再次执行验证流程。
</Warning>

您只能删除自己的账户通过本 API 注册的端点。若 `apiNotificationId` 不存在或属于其他账户，会返回 HTTP `200`，`meta.status` 为 `400`，`meta.errorCode` 为 `VALIDATION_FAILED`：

```json theme={null}
{
  "correlationId": "0HNCJ2K1P9RQ4:00000003",
  "meta": {
    "status": 400,
    "data": {},
    "errorCode": "VALIDATION_FAILED",
    "error": {
      "apiNotificationId": "Notification endpoint not found."
    }
  }
}
```

<h2 id="idempotency">
  幂等性
</h2>

`x-returnhelper-idempotency-key` 请求头为选填。不带该请求头的调用会正常执行，但不具备防重复的保护。请参阅[幂等性](/zh-Hans/introduction#idempotency)。

<h2 id="related">
  相关
</h2>

* [列出 Notification Endpoints](/zh-Hans/api-reference/notification/list-notification-endpoints)
* [添加 Notification Endpoint](/zh-Hans/api-reference/notification/add-notification-endpoint)


## OpenAPI

````yaml post /api/Notification/Delete
openapi: 3.1.0
info:
  title: Return Helper API
  description: API documentation for Return Helper — covering User and Public endpoints.
  version: 1.0.0
servers:
  - url: https://api.returnshelper.com/uat/user
    description: Sandbox — User API
  - url: https://api.returnshelper.com/uat/public
    description: Sandbox — Public API
  - url: https://api.returnhelpercentre.com/v1/user
    description: Production — User API
  - url: https://api.returnhelpercentre.com/v1/public
    description: Production — Public API
  - url: https://api.returnhelperchina.com/user
    description: Production — User API (China)
security:
  - ApiKey: []
    ApiToken: []
paths:
  /api/Notification/Delete:
    post:
      tags:
        - Notification
      summary: Delete a notification endpoint
      operationId: ReturnUserApi_NotificationDelete
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/DeleteNotificationRequest'
      responses:
        '200':
          description: >-
            Success — returns the standard response envelope with no additional
            payload fields. Inspect meta.status to confirm the deletion
            succeeded.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiResponse'
        '401':
          description: >-
            Authentication failed. Returned when the `x-rr-apikey` or
            `x-rr-apitoken` header is missing or invalid. The body uses the
            standard `ApiResponse` envelope with `meta.error.message` describing
            the auth failure.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiResponse'
      security:
        - ApiKey: []
          ApiToken: []
      servers:
        - url: https://api.returnshelper.com/uat/user
          description: Sandbox — User API
components:
  schemas:
    DeleteNotificationRequest:
      type: object
      properties:
        apiNotificationId:
          type: integer
          format: int64
          description: >-
            Identifier of the notification endpoint to delete, as returned by
            /api/Notification/GetAll.
          examples:
            - 1234
      required:
        - apiNotificationId
    ApiResponse:
      type: object
      description: >-
        Universal response envelope. Successful responses include the business
        payload as additional top-level fields alongside `correlationId` and
        `meta`. Failed responses (auth errors, validation errors) only populate
        `correlationId` and `meta`, with `meta.errorCode` and `meta.error`
        describing the failure.
      properties:
        correlationId:
          type:
            - string
            - 'null'
          description: >-
            Unique correlation ID for tracing the request through Return Helper
            systems.
        meta:
          $ref: '#/components/schemas/ApiResponseMeta'
    ApiResponseMeta:
      type: object
      description: >-
        Application-level metadata for every API response. Inspect `status` and
        `errorCode` to detect soft-error responses (validation failures arrive
        as HTTP 200 with `meta.status: 400`).
      properties:
        status:
          type: integer
          description: >-
            Application-level status code. For successful operations this
            mirrors the HTTP status (e.g. 200). For validation failures it
            reports the logical status (e.g. 400) even though the wire HTTP
            status is 200.
        data:
          type: object
          additionalProperties:
            type: string
          description: Reserved free-form metadata key/value pairs. Usually empty.
        errorCode:
          type:
            - string
            - 'null'
          description: >-
            Machine-readable error code (e.g. `VALIDATION_FAILED`). Non-null
            only when the operation failed.
        error:
          type: object
          additionalProperties: true
          description: >-
            Field-level or message-level error detail keyed by request property
            name. Empty object on success.
  securitySchemes:
    ApiKey:
      type: apiKey
      in: header
      name: x-rr-apikey
      description: Your API key
    ApiToken:
      type: apiKey
      in: header
      name: x-rr-apitoken
      description: Your API token — keep this private

````