Skip to main content
Neon Docs

Search documentation

Type to search this documentation.

List project snapshots

GET/projects/{project_id}/snapshotsList project snapshots

Lists the snapshots for the specified project. Each snapshot represents a point-in-time backup of the project data.

Parameters

project_idstringpathrequired

The Neon project ID

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

Responses

200Projects snapshotsapplication/json
object
snapshotsarray of objectrequired
Show child attributes
Show array items
created_atstringrequired

Timestamp when the snapshot was created, in RFC 3339 format (UTC).

diff_sizeinteger · int64

Incremental Postgres storage size in bytes since the previous scheduled snapshot, when the snapshot is billed on incremental (diff) usage. When absent, either the incremental size has not been calculated yet and the snapshot is not being charged, or the snapshot is charged at full logical size (in that case `full_size` is set).

expires_atstring

RFC 3339 timestamp when the snapshot expires and is eligible for deletion. Null if the snapshot does not have an expiry.

full_sizeinteger · int64

Full logical size of the snapshot in bytes at the time it was taken. When absent, the logical size has not been calculated yet and the snapshot is not being charged. When present, a value of 0 means the snapshot is not being charged.

idstringrequired

The snapshot ID.

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

lsnstring

WAL position (Log Sequence Number) at which the snapshot was captured, in Postgres LSN format (for example, `0/3000000`).

manualboolean

True if the snapshot was created manually rather than by a schedule.

namestringrequired

Human-readable label for the snapshot.

slugstring

Snapshot resource ID, unique within the project. Distinct from the internal snapshot ID and display name.

source_branch_idstring

Branch from which this snapshot was created.

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

timestampstring

Point in time captured by the snapshot, in RFC 3339 format (UTC).

Example response
{
  "snapshots": [
    {
      "created_at": "2025-01-15T10:30:00Z",
      "diff_size": 0,
      "expires_at": "string",
      "full_size": 0,
      "id": "string",
      "lsn": "string",
      "manual": true,
      "name": "string",
      "slug": "string",
      "source_branch_id": "string",
      "timestamp": "string"
    }
  ]
}
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