> ## 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.
# 获取任意会话附件
> 获取只按 id 定位的会话中某个附件的元数据。
获取只按 id 定位的会话中某个附件的元数据。返回 `attachment_id`、`filename`、`size`、`content_type`、`content_disposition`、`content_id`，以及一个短时效的 `download_url` 和 `expires_at`。字节内容不内联，需在过期前去取 `download_url`。这是账号级视图，跨越账号下的每一个收件箱。所有 AIsa 调用方共用同一个 AgentMail 账号，因此这里会触及其他调用方创建的收件箱；只针对单个收件箱时请用收件箱级的孪生工具 `get_agentmail_inbox_thread_attachment`。
## 示例
```bash REST theme={null}
curl -X GET "https://api.aisa.one/apis/v1/agentmail/threads/{thread_id}/attachments/{attachment_id}" \
-H "Authorization: Bearer YOUR_API_KEY"
```
```jsonc MCP theme={null}
// 把整段复制给 Claude Code、Codex、Cursor 或任意 coding agent。
// 连接、授权、跑通这个例子需要的东西都在里面 ——
// 不用粘贴任何 key，浏览器里点一次 Allow 就好。
{
"operation_id": "get_agentmail_thread_attachment",
"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/get_agentmail-threads-thread-id-attachments-attachment-id.md
// Then run the call and show me the result.
```
**第一次用？** 把任意 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)。
[在你的 agent 里把这个端点跑起来 →](https://aisa.one/mcp?from=/zh/api-reference/agentmail/get_agentmail-threads-thread-id-attachments-attachment-id)
## OpenAPI
````yaml openapi/zh/agentmail.json GET /agentmail/threads/{thread_id}/attachments/{attachment_id}
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/threads/{thread_id}/attachments/{attachment_id}:
get:
tags:
- subpackage_threads
summary: 获取任意会话附件
description: >-
获取只按 id 定位的会话中某个附件的元数据。返回
`attachment_id`、`filename`、`size`、`content_type`、`content_disposition`、`content_id`，以及一个短时效的
`download_url` 和 `expires_at`。字节内容不内联，需在过期前去取
`download_url`。这是账号级视图，跨越账号下的每一个收件箱。所有 AIsa 调用方共用同一个 AgentMail
账号，因此这里会触及其他调用方创建的收件箱；只针对单个收件箱时请用收件箱级的孪生工具
`get_agentmail_inbox_thread_attachment`。
operationId: get_agentmail_thread_attachment
parameters:
- name: thread_id
in: path
required: true
schema:
$ref: '#/components/schemas/type_threads_ThreadId'
- name: attachment_id
in: path
required: true
schema:
$ref: '#/components/schemas/type_attachments_AttachmentId'
- name: Authorization
in: header
description: Bearer 身份验证
required: true
schema:
type: string
responses:
'200':
description: 状态码为 200 的响应
content:
application/json:
schema:
$ref: '#/components/schemas/type_attachments_AttachmentResponse'
'404':
description: 状态码为 404 的错误响应
content:
application/json:
schema:
$ref: '#/components/schemas/type__ErrorResponse'
components:
schemas:
type_threads_ThreadId:
type: string
description: 会话 ID。
title: ThreadId
type_attachments_AttachmentId:
type: string
description: 附件 ID。
title: AttachmentId
type_attachments_AttachmentResponse:
type: object
properties:
attachment_id:
$ref: '#/components/schemas/type_attachments_AttachmentId'
filename:
$ref: '#/components/schemas/type_attachments_AttachmentFilename'
size:
$ref: '#/components/schemas/type_attachments_AttachmentSize'
content_type:
$ref: '#/components/schemas/type_attachments_AttachmentContentType'
content_disposition:
$ref: '#/components/schemas/type_attachments_AttachmentContentDisposition'
content_id:
$ref: '#/components/schemas/type_attachments_AttachmentContentId'
download_url:
type: string
description: 用于下载附件的 URL。
expires_at:
type: string
format: date-time
description: 下载 URL 的过期时间。
required:
- attachment_id
- size
- download_url
- expires_at
title: AttachmentResponse
type__ErrorResponse:
type: object
properties:
name:
$ref: '#/components/schemas/type__ErrorName'
message:
$ref: '#/components/schemas/type__ErrorMessage'
required:
- name
- message
title: ErrorResponse
type_attachments_AttachmentFilename:
type: string
description: 附件文件名。
title: AttachmentFilename
type_attachments_AttachmentSize:
type: integer
description: 附件大小（字节）。
title: AttachmentSize
type_attachments_AttachmentContentType:
type: string
description: 附件的内容类型。
title: AttachmentContentType
type_attachments_AttachmentContentDisposition:
type: string
enum:
- inline
- attachment
description: 附件的内容处置方式。
title: AttachmentContentDisposition
type_attachments_AttachmentContentId:
type: string
description: 附件的内容 ID。
title: AttachmentContentId
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.