Cancel an answer

October 12, 2026

Table of contents

  1. Request Headers
  2. Responses
  3. Model
  4. Examples
  5. Try It

Stop the answer Muse is working on in a chat, like the stop button in the muse.ai app. The stream shows turn.done with status: "interrupted". The chat stays: send the next message with POST /chats/chatId/messages.

https://api.useapi.net/v1/muse/chats/chatId/cancel

  • chatId is URL-encoded in the path (it contains : and @).
Request Headers 
Authorization: Bearer {API token}
Responses

  • 200 OK — cancelled is true when Muse confirmed the stop.

    {
  "chatId": "c-u12345-email:[email protected]:272b73f4-6fcb-42c2-9ec7-75cc0c020940-bot:muse",
  "cancelled": true
}

    cancelled is false when no answer was running.

  • 400 Bad Request — the path value is not a Muse chatId.

    {
  "error": "Path parameter chatId (not-a-chat-id) is not a valid Muse chat id",
  "code": 400
}

  • 401 Unauthorized

    Invalid API token.

    {
  "error": "useapi.net ⁝ Unauthorized",
  "code": 401
}

  • 403 Forbidden — the chatId was issued to a different API token.

    {
  "error": "This chat id does not belong to this API token",
  "code": 403
}

  • 404 Not Found — Muse has no such chat, or the account that holds the chat is not added.

    {
  "error": "Chat not found",
  "code": 404
}

    {
  "error": "Account [email protected] (from the chat id) is not configured",
  "code": 404
}

  • 503 Service Unavailable — Muse could not be reached. Retry shortly.

    {
  "error": "Could not connect to the Muse workspace of account [email protected] (…), please retry shortly",
  "code": 503
}

  • 596 Account Error

    The account needs your attention, and it is paused until you add it again. You receive an email when this happens. There are two causes.

    Meta asks for a security check on the account. Sign in once at muse.ai in a browser, complete the check, then add the account again with POST /accounts using the same email and password. The API keeps using its session, so no new sign-in is needed.

    {
  "error": "Account [email protected]: Meta asks for a security check on account [email protected] (\"This account must complete a security checkpoint on the web\"). Sign in once at https://muse.ai in a browser, complete the check, then add the account again with POST /accounts",
  "code": 596
}

    Or Muse refused to sign the account in again when its session needed renewing, most often because the password was changed. Add the account again with the current password.

    {
  "error": "Account [email protected]: Muse refused to sign in account [email protected] (…). Update its password with POST /accounts, or sign in at https://muse.ai to clear the block, then re-add it",
  "code": 596
}
Model 
{ // TypeScript, all fields are optional
  chatId: string
  cancelled: boolean   // true when Muse confirmed the stop, false when no answer was running
  error?: string       // errors only
  code?: number        // errors only
}
Examples 
  • CHATID="c-u12345-email:[email protected]:272b73f4-6fcb-42c2-9ec7-75cc0c020940-bot:muse"
curl -X POST -H "Authorization: Bearer …" \
     "https://api.useapi.net/v1/muse/chats/$(python3 -c "import urllib.parse,sys;print(urllib.parse.quote(sys.argv[1],safe=''))" "$CHATID")/cancel"

  • const token = "API token";
const chatId = "chatId from POST /chats";
const apiUrl = `https://api.useapi.net/v1/muse/chats/${encodeURIComponent(chatId)}/cancel`;
const response = await fetch(apiUrl, {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${token}`,
  },
});
const result = await response.json();
console.log("response", response.status, result);

  • import requests
from urllib.parse import quote
token = "API token"
chatId = "chatId from POST /chats"
apiUrl = f"https://api.useapi.net/v1/muse/chats/{quote(chatId, safe='')}/cancel"
headers = {
    "Authorization" : f"Bearer {token}"
}
response = requests.post(apiUrl, headers=headers)
print(response, response.json())
Try It