Update database
API Reference / Branches / Update database
PATCH /projects//branches//databases/
Section titled “PATCH /projects//branches//databases/”Updates the specified database in the branch. For related information, see Manage databases.
Parameters
Section titled “Parameters”project_id(string, path, required) The Neon project IDbranch_id(string, path, required) The branch IDdatabase_name(string, path, required) The database name
Request body
Section titled “Request body”database(object, required) Properties to update on the database.-
name(string, optional) Name of the database to update. -
owner_name(string, optional) The name of the role that owns the database
-
{
"database": {
"name": "mydb",
"owner_name": "sally"
}
}Response (200)
Section titled “Response (200)”{
"database": {
"id": 1000000,
"branch_id": "br-young-forest-a5b6c7d8",
"name": "my-database-5",
"owner_name": "alex",
"created_at": "2025-01-15T10:30:00Z",
"updated_at": "2025-01-15T10:30:00Z"
},
"operations": []
}Code examples
Section titled “Code examples”curl "https://console.neon.tech/api/v2/projects/$PROJECT_ID/branches/$BRANCH_ID/databases/$DATABASE_NAME" \
-X PATCH \
-H "Authorization: Bearer $NEON_API_KEY" \
-H "Content-Type: application/json" \
-d '{"database":{"name":"mydb","owner_name":"sally"}}'import { createNeonClient, raw } from '@neon/sdk';
const neon = createNeonClient({ apiKey: process.env.NEON_API_KEY });
const { data } = await raw.updateProjectBranchDatabase({
client: neon.client,
path: {
project_id: process.env.PROJECT_ID,
branch_id: process.env.BRANCH_ID,
database_name: process.env.DATABASE_NAME
},
body: {
database: {
name: "mydb",
owner_name: "sally"
}
}
});Console
Section titled “Console”Console path: Projects → Branches → Roles & Databases
Errors
Section titled “Errors”default General Error.
The request may or may not be safe to retry, depending on the HTTP method, response status code, and whether a response was received.
- If no response is returned from the API, a network error or timeout likely occurred.
- In some cases, the request may have reached the server and been successfully processed, but the response failed to reach the client. As a result, retrying non-idempotent requests can lead to unintended results.
The following HTTP methods are considered non-idempotent: POST, PATCH, DELETE, and PUT. Retrying these methods is generally not safe.
The following methods are considered idempotent: GET, HEAD, and OPTIONS. Retrying these methods is safe in the event of a network error or timeout.
Any request that returns a 503 Service Unavailable response is always safe to retry.
Any request that returns a 423 Locked response is safe to retry. 423 Locked indicates that the resource is temporarily locked, for example, due to another operation in progress.
-
request_id(string, optional) Unique identifier for the request, useful for debugging. You can set this value manually by including anX-Request-IDheader in the request. If not provided, the value will be generated automatically. -
code(string, required) Machine-readable code classifying the error type. Seemessagefor a human-readable explanation. Default: `` -
message(string, required) Error message