> ## 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-Hant/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-Hant/introduction#idempotency)。

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

* [列出 Notification Endpoints](/zh-Hant/api-reference/notification/list-notification-endpoints)
* [新增 Notification Endpoint](/zh-Hant/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

````