> ## 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.

> ## Agent Instructions
> - Base URLs: models `https://api.aisa.one/v1` (Gemini GenerateContent: `https://api.aisa.one/v1beta`); data APIs `https://api.aisa.one/apis/v1`. The `servers` of each operation in https://aisa.one/openapi.yaml is authoritative.
> - Auth: `Authorization: Bearer $AISA_API_KEY`. Never print, log, or commit the key.
> - MCP (preferred for agents): `https://mcp.aisa.one/mcp`, signed in with OAuth, so there is no key to paste.
> - Agent Skill: `npx skills add AIsa-team/agent-skills --skill aisa`. Fallback with the AIsa CLI: `aisa skills install aisa`.
> - Spending: docs, https://aisa.one/models, https://aisa.one/api, `/v1/models`, and MCP `search`, `list_categories`, `get_details`, `batch_quote`, and the `account` operation are free. Quote the exact calls before running them (MCP `batch_quote`, CLI `aisa quote --json`). If the quote reports `auto_execute_eligible: true`, run it unless the user set a tighter limit or asked only for a quote. Otherwise, tell the user in one message the planned calls, the quoted price, and a total USD budget for the task, then wait for approval. Direct HTTP calls follow the stricter rule at https://aisa.one/docs/get-started/cli.md#direct-http-fallback. Do not make paid calls to test availability. Full rule: https://aisa.one/llms.txt

# Change who answers a conversation (handover)

> Inbox. Acts in public on your connected account; needs social:publish. Audited. Ids are yours: accounts acc_..., profiles prf_..., posts pst_...; every other object id is checked against your accounts before the call.

Changes who answers a conversation, using Meta's handover protocol on WhatsApp, Facebook and Instagram.

**WhatsApp**, on numbers with Meta Business Agent enabled:

- `release`: hand the conversation back to the agent so it resumes answering. You must currently hold control (sending any message takes it implicitly).
- `take`: take control before sending anything, so the agent stops replying while an operator reads the thread. Meta accepts this only from the business configured as the number's escalation partner; other apps take control by sending a message.
- `pass`: transfer control to the number's configured escalation partner, or to the agent with `target: ai_agent`. Meta's Cloud API currently rejects it ("Pass action is not supported", verified 2026-09-08); use `release` to hand a thread back to the agent.

**Facebook and Instagram** (Messenger Platform handover between the apps on the Page, such as Page Inbox):

- `pass` with `targetAppId`: give the thread to another app (`pass_thread_control`). Page Inbox is 263902037430900.
- `take`: take the thread back (`take_thread_control`). Meta allows it only to the Page's primary receiver, and only on accounts connected through a Facebook Page. On an Instagram Login connection it answers 400 `platform_not_supported`.
- `request`: ask the current owner to pass the thread (`request_thread_control`); nothing changes until it does. Not available on Instagram Login connections (400 `platform_not_supported`).
- `release`: give the thread back to the primary receiver (`release_thread_control`).

### While another app owns the thread

While another app owns a Facebook or Instagram thread, inbound messages arrive with `metadata.standby: true` and a send answers 409 `not_thread_owner`.

The conversation's `threadControl` follows the result. A `conversation.control_changed` webhook fires when Meta later reports the change.

<!-- aisa-pricing:start -->
当前未提供请求参考价格；请使用接口支持的报价功能确认费用。 最终费用以账户适用价格及实际结算为准。
<!-- aisa-pricing:end -->

## 请求规范

* **方法与路径:** POST /apis/v1/social/inbox/conversations/\{conversationId}/thread-control
* **可用状态:** enabled
* **请求 URL 模板:** `https://api.aisa.one/apis/v1/social/inbox/conversations/{conversationId}/thread-control`
* **conversationId:** path; 必填
* **Runtime 事实版本:** 99acb5bddbedc8d3352e7c4fef86c3e6d8852c14772bcd18dbcf415237a642bd

[完整 OpenAPI 定义](https://aisa.one/docs/reference-contracts/zh/aisa-social.json)

有效请求与价格声明（包括认证和引用的 schema）：

```json theme={null}
{
  "operationId": "post_aisa_social_apis_v1_social_inbox_conversatio_e875e9",
  "method": "POST",
  "path": "/apis/v1/social/inbox/conversations/{conversationId}/thread-control",
  "servers": [
    {
      "url": "https://api.aisa.one"
    }
  ],
  "parameters": [
    {
      "description": "The conversation ID",
      "in": "path",
      "name": "conversationId",
      "required": true,
      "schema": {
        "type": "string"
      }
    }
  ],
  "security": [
    {
      "bearerAuth": []
    }
  ],
  "requestBody": {
    "content": {
      "application/json": {
        "example": {
          "accountId": "acc_7Hq2Lm9Xc4Rt8Vw1Nb6Ks3",
          "action": "pass",
          "metadata": "Customer asked for a human",
          "targetAppId": "263902037430900"
        },
        "schema": {
          "properties": {
            "accountId": {
              "description": "One of your social accounts (acc_...).",
              "pattern": "^acc_[0-9A-Za-z]{22}$",
              "type": "string"
            },
            "action": {
              "description": "`request` is Facebook and Instagram only. `take` and `request` are refused with `platform_not_supported` on Instagram accounts connected with Instagram Login.",
              "enum": [
                "release",
                "take",
                "pass",
                "request"
              ],
              "type": "string"
            },
            "metadata": {
              "description": "Free-form note forwarded verbatim to the app receiving control (its messaging_handovers webhook).",
              "maxLength": 2000,
              "type": "string"
            },
            "target": {
              "description": "WhatsApp only. With action pass: send control to Meta Business Agent instead of the escalation partner.",
              "enum": [
                "ai_agent"
              ],
              "type": "string"
            },
            "targetAppId": {
              "description": "Facebook and Instagram only, required with action pass: the Meta app id receiving the thread.",
              "pattern": "^[0-9]+$",
              "type": "string"
            }
          },
          "required": [
            "accountId",
            "action"
          ],
          "type": "object"
        }
      }
    },
    "required": true
  },
  "x-aisa-status": "enabled",
  "x-aisa-pricing": {
    "description": "Included with your connected social accounts: AIsa does not charge per call.",
    "kind": "no_customer_charge"
  },
  "components": {
    "securitySchemes": {
      "bearerAuth": {
        "scheme": "bearer",
        "type": "http"
      }
    }
  }
}
```

## 费用与请求规则

当前未提供请求参考价格；请使用接口支持的报价功能确认费用。 最终费用以账户适用价格及实际结算为准。

公开参考值不是你的账户报价或最终扣费。对于支持 X-AISA-Cost-Mode: quote 的接口，执行前请针对完整请求获取免费报价；执行后通过响应费用元数据和 Usage Logs 核对结算费用。1 USD 等于 1,000,000 个整数 micro-USD。


## OpenAPI

````yaml reference-contracts/zh/aisa-social.json POST /apis/v1/social/inbox/conversations/{conversationId}/thread-control
openapi: 3.1.0
info:
  description: ''
  title: AIsa Social
  version: '1'
  x-aisa-capabilities:
    idempotency: Idempotency-Key
    max_price: X-AISA-Max-Price-USD
    quote:
      header: X-AISA-Cost-Mode
      value: quote
  x-aisa-configured-paths: []
  x-aisa-document:
    facts_hash: 99acb5bddbedc8d3352e7c4fef86c3e6d8852c14772bcd18dbcf415237a642bd
    generator_version: '3'
    protocol_version: '1'
    schema_version: '1'
    composer_version: '27'
    response_pending: []
    document_hash: sha256:7f9742cb1ea233c648dcb290fdfbf24e53a27dcf900ec1386f83a8ef2e6b1bf9
  x-aisa-plans:
    builder: 1
    display_plan: payg
    payg: 1
    similarweb_payg: 1
    team: 1
    version: e70a0959cd1b93b84ae16dffd7a538273ddb9c1d46277b82823c37ff1b6bc0fb
  x-aisa-provider: aisa-social
  x-aisa-catalogs:
    aisa-social:
      title: AIsa Social
      description: ''
      x-aisa-document:
        facts_hash: 99acb5bddbedc8d3352e7c4fef86c3e6d8852c14772bcd18dbcf415237a642bd
        generator_version: '3'
        protocol_version: '1'
        schema_version: '1'
      x-aisa-plans:
        builder: 1
        display_plan: payg
        payg: 1
        similarweb_payg: 1
        team: 1
        version: e70a0959cd1b93b84ae16dffd7a538273ddb9c1d46277b82823c37ff1b6bc0fb
      x-aisa-capabilities:
        idempotency: Idempotency-Key
        max_price: X-AISA-Max-Price-USD
        quote:
          header: X-AISA-Cost-Mode
          value: quote
servers:
  - url: https://api.aisa.one
security:
  - bearerAuth: []
paths:
  /apis/v1/social/inbox/conversations/{conversationId}/thread-control:
    post:
      summary: Change who answers a conversation (handover)
      description: >-
        Inbox. Acts in public on your connected account; needs social:publish.
        Audited. Ids are yours: accounts acc_..., profiles prf_..., posts
        pst_...; every other object id is checked against your accounts before
        the call.


        Changes who answers a conversation, using Meta's handover protocol on
        WhatsApp, Facebook and Instagram.


        **WhatsApp**, on numbers with Meta Business Agent enabled:


        - `release`: hand the conversation back to the agent so it resumes
        answering. You must currently hold control (sending any message takes it
        implicitly).

        - `take`: take control before sending anything, so the agent stops
        replying while an operator reads the thread. Meta accepts this only from
        the business configured as the number's escalation partner; other apps
        take control by sending a message.

        - `pass`: transfer control to the number's configured escalation
        partner, or to the agent with `target: ai_agent`. Meta's Cloud API
        currently rejects it ("Pass action is not supported", verified
        2026-09-08); use `release` to hand a thread back to the agent.


        **Facebook and Instagram** (Messenger Platform handover between the apps
        on the Page, such as Page Inbox):


        - `pass` with `targetAppId`: give the thread to another app
        (`pass_thread_control`). Page Inbox is 263902037430900.

        - `take`: take the thread back (`take_thread_control`). Meta allows it
        only to the Page's primary receiver, and only on accounts connected
        through a Facebook Page. On an Instagram Login connection it answers 400
        `platform_not_supported`.

        - `request`: ask the current owner to pass the thread
        (`request_thread_control`); nothing changes until it does. Not available
        on Instagram Login connections (400 `platform_not_supported`).

        - `release`: give the thread back to the primary receiver
        (`release_thread_control`).


        ### While another app owns the thread


        While another app owns a Facebook or Instagram thread, inbound messages
        arrive with `metadata.standby: true` and a send answers 409
        `not_thread_owner`.


        The conversation's `threadControl` follows the result. A
        `conversation.control_changed` webhook fires when Meta later reports the
        change.


        <!-- aisa-pricing:start -->

        当前未提供请求参考价格；请使用接口支持的报价功能确认费用。 最终费用以账户适用价格及实际结算为准。

        <!-- aisa-pricing:end -->
      operationId: post_aisa_social_apis_v1_social_inbox_conversatio_e875e9
      parameters:
        - description: The conversation ID
          in: path
          name: conversationId
          required: true
          schema:
            type: string
      requestBody:
        content:
          application/json:
            example:
              accountId: acc_7Hq2Lm9Xc4Rt8Vw1Nb6Ks3
              action: pass
              metadata: Customer asked for a human
              targetAppId: '263902037430900'
            schema:
              properties:
                accountId:
                  description: One of your social accounts (acc_...).
                  pattern: ^acc_[0-9A-Za-z]{22}$
                  type: string
                action:
                  description: >-
                    `request` is Facebook and Instagram only. `take` and
                    `request` are refused with `platform_not_supported` on
                    Instagram accounts connected with Instagram Login.
                  enum:
                    - release
                    - take
                    - pass
                    - request
                  type: string
                metadata:
                  description: >-
                    Free-form note forwarded verbatim to the app receiving
                    control (its messaging_handovers webhook).
                  maxLength: 2000
                  type: string
                target:
                  description: >-
                    WhatsApp only. With action pass: send control to Meta
                    Business Agent instead of the escalation partner.
                  enum:
                    - ai_agent
                  type: string
                targetAppId:
                  description: >-
                    Facebook and Instagram only, required with action pass: the
                    Meta app id receiving the thread.
                  pattern: ^[0-9]+$
                  type: string
              required:
                - accountId
                - action
              type: object
        required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                properties:
                  control:
                    properties:
                      owner:
                        enum:
                          - app
                          - ai_agent
                          - other
                        type: string
                      ownerAppId:
                        description: >-
                          The app that received the thread, on a Facebook or
                          Instagram pass.
                        type: string
                    type: object
                  success:
                    type: boolean
                type: object
          description: Control transferred (or, for request, asked for)
        default:
          content:
            application/json:
              schema:
                properties:
                  error:
                    properties:
                      code:
                        type:
                          - string
                          - 'null'
                      details:
                        additionalProperties: {}
                        type:
                          - object
                          - 'null'
                      message:
                        type:
                          - string
                          - 'null'
                      param:
                        type:
                          - string
                          - 'null'
                      retryHint:
                        enum:
                          - never
                          - after_delay
                          - after_reconnect
                          - reconcile_first
                          - null
                        type:
                          - string
                          - 'null'
                      retryable:
                        type:
                          - boolean
                          - 'null'
                      type:
                        type:
                          - string
                          - 'null'
                    type:
                      - object
                      - 'null'
                type: object
          description: Error. The code field is stable; see the error catalog.
components:
  securitySchemes:
    bearerAuth:
      scheme: bearer
      type: http

````

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