Skip to main content
Neon Docs

Search documentation

Type to search this documentation.

Retrieve backup schedule

GET/projects/{project_id}/branches/{branch_id}/backup_scheduleRetrieve backup schedule

Returns the backup schedule for the specified branch, including the configured snapshot frequencies.

Parameters

project_idstringpathrequired

The Neon project ID

pattern ^[a-z0-9-]{1,60}$

branch_idstringpathrequired

The branch ID

pattern ^[a-z0-9-]{1,60}$

Responses

200Schedule of frequencies to create snapshotsapplication/json
objectBackupSchedule
schedulearray of objectrequired

List of schedule entries defining the backup frequency. At least one entry is required.

Show child attributes
Show array items
dayinteger

The day of the week or month to take the snapshot (if applicable).

maximum 31 · minimum 1

frequencystringrequired

How often to take snapshots. Known values: `daily`, `weekly`, `monthly`.

hourinteger

The hour of the day to take the snapshot (if applicable).

maximum 23 · minimum 0

monthinteger

The month of the year to take the snapshot (if applicable).

maximum 12 · minimum 1

retention_secondsinteger

How long to keep a scheduled snapshot (in seconds) before it's automatically deleted. The default is 3024000 seconds (35 days), which is also the maximum. Manually created snapshots have no maximum retention: set their `expires_at` instead.

default 3024000 · maximum 3024000 · minimum 3600

Example response
{
  "schedule": [
    {
      "day": 0,
      "frequency": "daily",
      "hour": 0,
      "month": 0,
      "retention_seconds": 3024000
    }
  ]
}
defaultGeneral 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. application/json
objectGeneralError
codestringrequired

default ""

messagestringrequired

Error message

request_idstring

Unique identifier for the request, useful for debugging. You can set this value manually by including an `X-Request-ID` header in the request. If not provided, the value will be generated automatically.

Example response
{
  "code": "",
  "message": "string",
  "request_id": "string"
}
Documentation menu