> ## 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 Endpoint を一覧取得](/ja/api-reference/notification/list-notification-endpoints)で返される `apiNotificationId` を指定して、登録済みの通知エンドポイントを 1 件削除します。1 回の呼び出しで削除できるのは 1 件です。レスポンスにペイロードはありません——`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` ヘッダーは任意です。付与しない呼び出しも通常どおり実行されますが、重複に対する保護はありません。[冪等性](/ja/introduction#idempotency)を参照してください。

<h2 id="related">
  関連
</h2>

* [Notification Endpoint を一覧取得](/ja/api-reference/notification/list-notification-endpoints)
* [Notification Endpoint を追加](/ja/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

````