Skip to main content
POST
Create Application Snapshot
string
required
The ID of the application or database to snapshot.
string
required
The resource type. Possible values: applications, databases.
Three limits apply to manual snapshots, on top of the route’s 5 requests per minute. The same resource can be snapshotted once every 5 minutes and up to 5 times per day, and an account can create, across all its resources, a number of snapshots per day that depends on the plan (5 on Starter 1 and 2, up to 64 on Enterprise). The day follows Brasília time. Over any limit the API answers 429 SNAPSHOT_RATE_LIMITED with details.scope (resource, resource_daily or account) and details.retry_after in seconds; with resource_daily and account, details also has limit and resets_at, the moment the budget resets, in ISO 8601. Snapshots the platform takes on its own (before a reset or a stack or image delete) do not count. A snapshot can be at most 4 GB (the compressed file). See Rate Limiting.

Response

object
The snapshot that was created.

Error Responses

string
The error code indicating the reason for failure. Possible values:
  • AUTH_TOKEN_MISSING, API_KEY_INVALID, SESSION_REVOKED: The Authorization header is missing, the API key is invalid, or the dashboard session was revoked (401).
  • API_KEY_IP_DENIED, API_KEY_SCOPE_DENIED: The API key is used from an IP outside its allowlist, or it lacks the scope the route requires (403).
  • USER_NOT_FOUND: The authenticated user was not found.
  • APP_NOT_FOUND: The specified application does not exist.
  • DATABASE_NOT_FOUND: The specified database does not exist.
  • ACCESS_DENIED: The user does not own the resource.
  • PLAN_NOT_ALLOWED: The account’s plan does not include manual snapshots (403).
  • DATABASE_NOT_RUNNING: The database must be running to take a snapshot (409). Redis has no such requirement.
  • SNAPSHOT_RATE_LIMITED: The resource was snapshotted less than 5 minutes ago, the resource already had 5 manual snapshots today, or the account already used its daily budget of manual snapshots (429). Comes with details.scope and details.retry_after; with resource_daily or account, also details.limit and details.resets_at.
  • SNAPSHOT_TOO_LARGE: The snapshot file would exceed the 4 GB limit (413).
  • OPERATION_IN_PROGRESS: Another lifecycle operation on the same resource is already running (409). Nothing was snapshotted — wait a few seconds and retry.
  • INTERNAL_SERVER_ERROR: The snapshot could not be stored, or an unexpected failure occurred (500). Retry later.
Last modified on November 8, 2026