apps

Update an app's name, description, or data-chat kill switch.

EDITOR is the endpoint's gate — renaming is ordinary editing. But data_chat_enabled is an ADMIN lever (it governs what an app hands out: the data chat can read any bound COLUMN, not only the ones the generated UI draws), so a patch that carries it requires ADMIN as well. Checked per-field rather than by re-gating the endpoint: raising the whole route to ADMIN would break ordinary renames, and letting an EDITOR flip the switch would make it not a kill switch.

patch/api/v1/apps/{app_id}

Request

  • Base URL
    https://api.netter.ai (the document declares no server; this is the origin it was published from)
  • URL
    https://api.netter.ai/api/v1/apps/{app_id}
  • Auth
    none declared

Path parameters

app_idstring uuid required

Request body

namestring nullable
descriptionstring nullable
data_chat_enabledboolean nullable

Response

Successful Response

idstring uuid required
company_idstring uuid required
user_idstring uuid required
namestring required
descriptionstring required
statusstring required
bundle_urlstring nullable required
bundle_cssstring nullable required
bundle_importsstring[] nullable required
error_messagestring nullable required
current_version_idstring uuid nullable required
collection_idstring uuid nullable
embed_inputsobject[] nullable
created_atstring date-time required
updated_atstring date-time required
is_favoriteboolean
data_chat_enabledboolean

Changes

    • info

      added the optional property to the response with the status

    • info

      added the new optional request property

    • info

      added the optional property to the response with the status