Patch apiv1orghomepage settings

Error

A valid request URL is required to generate request examples

{
  "results": {
    "opening": "ask-first",
    "enabled": true,
    "organizationUuid": "<string>"
  },
  "status": "ok"
}

{
  "error": {
    "name": "<string>",
    "statusCode": 123,
    "data": "<unknown>",
    "message": "<string>"
  },
  "status": "error"
}

PATCH

api

org

homepage-settings

Error

A valid request URL is required to generate request examples

{
  "results": {
    "opening": "ask-first",
    "enabled": true,
    "organizationUuid": "<string>"
  },
  "status": "ok"
}

{
  "error": {
    "name": "<string>",
    "statusCode": 123,
    "data": "<unknown>",
    "message": "<string>"
  },
  "status": "error"
}

Body

application/json

opening

enum<string> | null

required

Which hero opens the homepage: the Ask AI composer or greeting + quick actions. An admin's layout decision, independent of whether AI is licensed.

Available options:

ask-first,

content-first

enabled

boolean

required

Response

Success

results

object

required

Org-wide homepage v2 state. enabled turns the new homepage on for every project in the organization; the commercial flag remains as a kill-switch. opening: null means "auto" — AI availability decides, which is the legacy behaviour for orgs enabled via the flag before this setting existed.

Show child attributes

status

enum<string>

required

Available options:

ok