Managed Databases
Restore database
Changed onRestore a database to a backup or a point in time, either into a new database (clone_to_new: true) or over this one (in_place: true).
<Note> Before restoring, get a **backup ID** or the **restore window** from [List backups](/api-reference/databases/list-database-backups). </Note>Choose the restore point with backup_id (a completed backup with restorable: true) or, for PostgreSQL and MySQL on paid plans, pitr_timestamp (any time from restore_window_start on the backup list until now). Omit both to restore the latest available state. A point outside the window returns 400. Set exactly one of clone_to_new and in_place.
- New database: inherits the source's plan, storage, VPC, and project, starts with no read replicas, and bills pay-as-you-go. High availability is an explicit choice via ha_enabled, never inherited. If new_name is taken, the platform adds a suffix (-2, -3, …). Poll GET /api/v1/databases/{new_database_id} like any create. Free databases cannot restore into a new database.
- In place: overwrites this database. A safety backup is taken first, the status is restoring while it runs, and new_database_id is empty. Data written after the restore point is lost.
post/api/v1/databases/{database_id}/restore
Request
- Base URLhttps://api.rafftechnologies.com
- URLhttps://api.rafftechnologies.com/api/v1/databases/{database_id}/restore
- AuthAPI key in header X-API-Key
Path parameters
database_idstring required
Database ID (UUID) or short id (the database_id field, e.g. a1b2c3d4)
Request body
Response
Restore started
Changes
- info
added the new optional request property
- info
the request property
became optional
- info
- info
endpoint added
- info