Skip to main content
PATCH
Update database settings

Authorizations

Authorization
string
header
required

Session access JWT or an API token (insta_<prefix>_<secret>).

Path Parameters

projectId
string<uuid>
required

Query Parameters

branch
string

branch name (default branch if omitted)

group
string

postgres service name (default: the sole postgres service)

Body

application/json
connectionPooling
boolean

enable provider-managed PgBouncer/connection pooling

deletionProtection
boolean
scaleToZero
boolean

enable or disable scale-to-zero

cpu
string

resource ceiling — vCPU as a provider quantity ('2', '4', '2500m'). PAID PLANS: the ceiling is the tier lever. Moves both directions (insta-db only)

memory
string

resource ceiling — memory as a provider quantity ('4Gi', '8Gi'). PAID PLANS. Moves both directions (insta-db only)

idleTimeout
integer

scale-to-zero idle timeout in seconds

Required range: x >= 0
volumeSize
string

the volume (block disk) size cap as whole Gi ('10Gi'). PAID PLANS: the ceiling is the tier lever. Grow-only — a provisioned disk cannot shrink (insta-db only)

storageSize
string
deprecated

DEPRECATED alias of volumeSize — dropped next release

Response

Default Response

id
string
name
string
state
string
routeKey
string
host
string
port
integer
connectionPooling
boolean
deletionProtection
boolean
scaleToZero
boolean
idleTimeoutSecs
integer
volumeSize
string

the service's volume (block disk) size

Example:

"10Gi"

volumeGib
number
storageSize
string
deprecated

DEPRECATED alias of volumeSize — dropped next release

storageGiB
number
deprecated

DEPRECATED alias of volumeGib — dropped next release

enabledExtensions
string[]
cpuMilli
integer

current cpu ceiling in millicores (2000 = 2 vCPU)

memoryMib
integer

current memory ceiling in MiB

cap
object

this plan's maximum for the ceilings — render sliders with their plan-limit markers. These are the caller's own tier caps and they move with the plan (and with env overrides per deployment), so read them from THIS field rather than assuming a tier's numbers; the parenthetical example that used to live here said 'pro 4 vCPU/4Gi/10Gi' and was stale on all three by the time anyone noticed.