---
title: "Update app"
method: PUT
path: "/api/apps/{app_id}"
---

# Update app

`PUT /api/apps/{app_id}`

<Info>This API is in beta. Endpoints, fields, and behavior may still change, so avoid depending on it in production.</Info>

Changes the app's name, its description, or both.

Send only the fields you want to change. A field you leave out keeps its value.

Renaming doesn't change the app's address. Change that with [Change app slug](/api-reference/change-app-slug).

<Warning>This endpoint also accepts other app fields, but only `name` and `user_description` are part of this API. Don't send anything else. Other fields aren't covered by the contract and can change or be rejected without notice.</Warning>

## Path parameters

- `app_id` unknown, required

## Request body

- object
  - `name` string — New name for the app.
  - `user_description` string, nullable — New description for the app, or `null` to remove it.

## Response `200`

The app, with its new details.

- AppSummary — An app in a workspace, limited to the properties the caller requested.
  - `id` string, nullable — ID of the app.
  - `first_prompt_model_comparison` FirstPromptModelComparisonPublicState
    - `id` string, required
    - `client_creation_id` string, required
    - `models` string[], required
    - `status` 'preparing' | 'running' | 'failed' | 'selected' | 'cancelled', required
  - `name` string, nullable — Display name of the app.
  - `slug` string, nullable — URL slug for the app, auto generated from the name and app ID or set to a custom value, or `null` if the app has no slug yet. The published URL is built from it.
  - `user_description` string, nullable — Description of the app, or `null` if none was set. An app created without a `name` gets a generated description once a build turn changes it.
  - `created_by` string, nullable — Email of the user who created the app.
  - `created_date` string, date-time, nullable — Time the app was created, as a UTC timestamp in ISO 8601 format.
  - `updated_date` string, date-time, nullable — Time the app document was last written, as a UTC timestamp in ISO 8601 format.
  - `status` AppStatusResponse — The app's current build status.
    - `state` 'ready' | 'processing' | 'error', required — Where the app is in its build lifecycle. Ready means idle with no build in progress, processing means the app is being generated or modified, and error means the last build failed. This tracks building, not publishing.
    - `details` string, nullable — Human readable note about the current state, such as what is being processed or why it failed, or `null` when there is nothing to report.
    - `request_id` string, nullable — ID of the request that last changed the status, or `null` if the status has never changed. Useful when reporting an issue.
    - `last_updated_date` string, date-time, nullable — Time the status was last updated, as a UTC timestamp in ISO 8601 format.
    - `error_source` string, nullable — Where the failure originated when `state` is `error`, or `null` otherwise. A value of `paywall` means the work was blocked because the app's workspace has no credits left.
    - `paywall_context` PaywallStatusContextResponse
      - `billing_organization_id` string, required — ID of the billing organization the paywall was evaluated against.
      - `user_id` string, required — ID of the user the paywall was evaluated for.
      - `evaluated_at` string, date-time, required — Time the paywall condition was evaluated, as a UTC timestamp in ISO 8601 format.
  - `last_deployed_at` string, date-time, nullable — Time the app was last published, as a UTC timestamp in ISO 8601 format, or `null` if it has never been published.
  - `screenshot_url` string, nullable — URL of a screenshot of the published app. Captured shortly after each publish, so it can briefly lag or be `null` right after publishing.
  - `preview_screenshot_url` string, nullable — URL of a preview screenshot taken before publishing, distinct from `screenshot_url`, or `null` if none has been captured.
  - `main_branch_protected` boolean, nullable — Whether the app's main branch is protected, so changes to main must go through a branch that's merged back. Change it with [Set main branch protection](/api-reference/set-main-branch-protection).

## Other responses

- `401` — Missing or invalid credentials.
- `403` — You don't have access to this app, or it doesn't exist.
- `422` — Validation Error

## Changes

> 18 revisions in range; 1 not diffed.

- **2026-09-28** `28fc82924122` — 1 info
  - added the optional property `main_branch_protected` to the response with the `200` status
- **2026-09-24** `cf164639a9bf` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/adexad/apis/base44-app-management-api/changes/api/apps/:app_id/put.md)

---

[API](https://skmtc.dev/adexad/apis/base44-app-management-api.md) · [All operations](https://skmtc.dev/adexad/apis/base44-app-management-api/llms.txt) · [OpenAPI document](https://skmtc.dev/adexad/apis/base44-app-management-api/revisions/28fc82924122?raw)