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

# 删除收件箱名单项

> 从某个收件箱的放行/拦截名单中移除一条，无响应体。

从某个收件箱的放行/拦截名单中移除一条，无响应体。它会从此改变该收件箱接收或发送哪些邮件。`read_only` 为 true 的条目由平台托管、无法移除——先用 `get_agentmail_inbox_list_entry` 确认。写入的是共享 AgentMail 工作区：所有 AIsa 调用方共用同一个 AgentMail 账号，因此这里会触及其他调用方创建的收件箱，你写进去的东西下一个调用方也看得到、改得动。

## 示例

<CodeGroup>
  ```bash REST theme={null}
  curl -X DELETE "https://api.aisa.one/apis/v1/agentmail/inboxes/{inbox_id}/lists/{direction}/{type}/{entry}" \
    -H "Authorization: Bearer YOUR_API_KEY"
  ```

  ```jsonc MCP theme={null}
  // 把整段复制给 Claude Code、Codex、Cursor 或任意 coding agent。
  // 连接、授权、跑通这个例子需要的东西都在里面 ——
  // 不用粘贴任何 key，浏览器里点一次 Allow 就好。
  {
    "operation_id": "delete_agentmail_inbox_list_entry",
    "arguments": {},
    "max_price_usd": 0.05
  }
  // ── for the agent ─────────────────────────────────────────────────────────
  // Register the AIsa MCP server, then call its `use` tool with the JSON above.
  //   name       aisa
  //   endpoint   https://mcp.aisa.one/mcp
  //   transport  streamable-http
  //   auth       OAuth. The server publishes RFC 9728 metadata, so open a
  //              browser and the user clicks Allow once — nothing to paste.
  //              If AISA_API_KEY is set, send it as a bearer header instead.
  // Use your own MCP mechanism, not a hand-edited config file:
  //   Codex        codex mcp add aisa --url https://mcp.aisa.one/mcp
  //   Claude Code  claude mcp add --transport http -s user aisa https://mcp.aisa.one/mcp
  //   Cursor / VS Code   a "url" entry for https://mcp.aisa.one/mcp in the MCP config
  // The server lists five tools over https://mcp.aisa.one/servers worth of APIs:
  // search, get_details, use, batch_use, list_categories. search and
  // get_details are free; use is billed per call and max_price_usd refuses
  // anything above the cap before spending. This operation's full contract —
  // every argument, the response shape, the price and the pitfalls — is at
  //   https://aisa.one/docs/zh/api-reference/agentmail/delete_agentmail-inboxes-inbox-id-lists-direction-type-entry.md
  // Then run the call and show me the result.
  ```
</CodeGroup>

<Note>
  **第一次用？** 把任意 MCP 客户端指向 `https://mcp.aisa.one/mcp` —— Claude Code、
  Codex、Cursor、VS Code 都可以。鉴权走 OAuth：客户端打开浏览器，你点一次
  Allow，不需要粘贴任何 key。各客户端的具体命令和每次调用的价格见
  [aisa.one/zh-cn/mcp](https://aisa.one/zh-cn/mcp#connect)。
</Note>

[在你的 agent 里把这个端点跑起来 →](https://aisa.one/mcp?from=/zh/api-reference/agentmail/delete_agentmail-inboxes-inbox-id-lists-direction-type-entry)


## OpenAPI

````yaml openapi/zh/agentmail.json DELETE /agentmail/inboxes/{inbox_id}/lists/{direction}/{type}/{entry}
openapi: 3.1.0
info:
  title: AgentMail API
  version: 1.0.0
  description: 通过 AIsa 统一网关公开的 AgentMail 电子邮件 API 端点。改编自上游 docs.agentmail.to OpenAPI 规范。
servers:
  - url: https://api.aisa.one/apis/v1
security:
  - Bearer: []
paths:
  /agentmail/inboxes/{inbox_id}/lists/{direction}/{type}/{entry}:
    delete:
      tags:
        - subpackage_inboxes.subpackage_inboxes/lists
      summary: 删除收件箱名单项
      description: >-
        从某个收件箱的放行/拦截名单中移除一条，无响应体。它会从此改变该收件箱接收或发送哪些邮件。`read_only` 为 true
        的条目由平台托管、无法移除——先用 `get_agentmail_inbox_list_entry` 确认。写入的是共享 AgentMail
        工作区：所有 AIsa 调用方共用同一个 AgentMail
        账号，因此这里会触及其他调用方创建的收件箱，你写进去的东西下一个调用方也看得到、改得动。
      operationId: delete_agentmail_inbox_list_entry
      parameters:
        - name: inbox_id
          in: path
          required: true
          schema:
            $ref: '#/components/schemas/type_inboxes_InboxId'
        - name: direction
          in: path
          required: true
          schema:
            $ref: '#/components/schemas/type_lists_Direction'
        - name: type
          in: path
          required: true
          schema:
            $ref: '#/components/schemas/type_lists_ListType'
        - name: entry
          in: path
          description: 电子邮件地址或域名。
          required: true
          schema:
            type: string
        - name: Authorization
          in: header
          description: Bearer 身份验证
          required: true
          schema:
            type: string
      responses:
        '200':
          description: 成功响应
        '404':
          description: 状态码为 404 的错误响应
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/type__ErrorResponse'
components:
  schemas:
    type_inboxes_InboxId:
      type: string
      description: 收件箱的 ID。
      title: InboxId
    type_lists_Direction:
      type: string
      enum:
        - send
        - receive
        - reply
      description: 列表条目的方向。
      title: Direction
    type_lists_ListType:
      type: string
      enum:
        - allow
        - block
      description: 列表条目的类型。
      title: ListType
    type__ErrorResponse:
      type: object
      properties:
        name:
          $ref: '#/components/schemas/type__ErrorName'
        message:
          $ref: '#/components/schemas/type__ErrorMessage'
      required:
        - name
        - message
      title: ErrorResponse
    type__ErrorName:
      type: string
      description: 错误名称。
      title: ErrorName
    type__ErrorMessage:
      type: string
      description: 错误消息。
      title: ErrorMessage
  securitySchemes:
    Bearer:
      type: http
      scheme: bearer

````

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