---
title: "List project snapshots"
method: GET
path: "/projects/{project_id}/snapshots"
tags: ["Snapshot"]
---

# List project snapshots

`GET /projects/{project_id}/snapshots`

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

**Note**: This endpoint is currently in Beta.

## Response `200`

Projects snapshots

- object
  - `snapshots` Snapshot[], required
    - `id` string, required
    - `name` string, required
    - `lsn` string
    - `timestamp` string
    - `source_branch_id` string
    - `created_at` string, required
    - `expires_at` string
    - `manual` boolean
    - `full_size` integer — 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.
    - `diff_size` integer — Incremental 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).

## Other responses

- `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.

---

[API](https://skmtc.net/neon/apis/neon-api.md) · [All operations](https://skmtc.net/neon/apis/neon-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/neon/neon-api/revisions/cfde79a5c713/schema)