Change permission defaults

October 12, 2026 (November 16, 2026)

Table of contents

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

Set whether the Muse agent on this account asks before it acts. This is the same setting as in the muse.ai app.

  • web covers the websites the agent reaches, for example while it runs code.
  • connectors covers actions in the apps connected to the Muse account, such as email or calendar.

Each one is auto_allow or always_ask:

  • auto_allow is Muse’s “Ask for some actions”, the default. Muse may act without asking, for example send an email from a connected Gmail.
  • always_ask is Muse’s “Always ask”. Muse asks before each such action, and the question comes to the chat as an approval.

Send one or both. Rules for single websites and app actions stay as they are, see GET /accounts/email/permissions.

https://api.useapi.net/v1/muse/accounts/email/permissions

  • email is the email of an added account, URL-encoded in the path.
Request Headers
Authorization: Bearer {API token}
Content-Type: application/json
Request Body
{
  "web": "always_ask",
  "connectors": "always_ask"
}
  • web is optional, the setting for websites.
    Supported values: auto_allow, always_ask.
  • connectors is optional, the setting for connected apps.
    Supported values: auto_allow, always_ask.

Send at least one of them.

Responses
  • 200 OK — the settings as they are now.

    {
      "email": "example@gmail.com",
      "defaults": {
        "web": "always_ask",
        "connectors": "always_ask"
      }
    }
    
  • 400 Bad Request — neither web nor connectors was sent, or a value is not supported.

    {
      "error": "Pass web and/or connectors (auto_allow or always_ask)",
      "code": 400
    }
    
  • 401 Unauthorized — Invalid API token.

    {
      "error": "useapi.net ⁝ Unauthorized",
      "code": 401
    }
    
  • 404 Not Found — the account named by email is not added.

    {
      "error": "Account example@gmail.com is not configured",
      "code": 404
    }
    
  • 503 Service Unavailable — Muse could not be read right now. Retry shortly.

    {
      "error": "Muse could not be read right now (…), please retry",
      "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 three 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 example@gmail.com: Meta asks for a security check on account example@gmail.com (\"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 example@gmail.com: Muse refused to sign in account example@gmail.com (…). Update its password with POST /accounts, or sign in at https://muse.ai to clear the block, then re-add it",
      "code": 596
    }
    

    Or Muse disabled the account’s computer and refuses to start it again. Sign in at muse.ai in a browser to see why, and ask Muse support to restore it with the form Muse shows there. Add the account again only after Muse has restored it.

    {
      "error": "Account example@gmail.com: Muse has disabled the computer of account example@gmail.com (\"VM wake unavailable\"). Sign in at https://muse.ai in a browser to see why and contact Muse support there, then add the account again with POST /accounts",
      "code": 596
    }
    
Model

The account’s two default settings, web and connectors, as they are after the change.

The account's default settings, field by field
{ // TypeScript, all fields are optional
  email: string
  defaults: {
    web: 'auto_allow' | 'always_ask' | null
    connectors: 'auto_allow' | 'always_ask' | null
  }
  error?: string               // errors only
  code?: number                // errors only
}
Examples
  • EMAIL="example@gmail.com"
    curl -X POST -H "Authorization: Bearer …" \
         -H "Content-Type: application/json" \
         -d '{"connectors": "always_ask"}' \
         "https://api.useapi.net/v1/muse/accounts/$(python3 -c "import urllib.parse,sys;print(urllib.parse.quote(sys.argv[1],safe=''))" "$EMAIL")/permissions"
    
  • const token = "API token";
    const email = "Previously added account email";
    const apiUrl = `https://api.useapi.net/v1/muse/accounts/${encodeURIComponent(email)}/permissions`;
    const response = await fetch(apiUrl, {
      method: "POST",
      headers: {
        "Content-Type": "application/json",
        "Authorization": `Bearer ${token}`,
      },
      body: JSON.stringify({ connectors: "always_ask" })
    });
    console.log("response", response.status, await response.json());
    
  • import requests
    from urllib.parse import quote
    token = "API token"
    email = "Previously added account email"
    apiUrl = f"https://api.useapi.net/v1/muse/accounts/{quote(email, safe='')}/permissions"
    headers = {
        "Content-Type": "application/json",
        "Authorization" : f"Bearer {token}"
    }
    response = requests.post(apiUrl, headers=headers, json={"connectors": "always_ask"})
    print(response, response.json())
    
Try It