Storage destinations
Endpoints for the storage destinations of the team: S3-compatible storage or SFTP servers the team owns, where the agents write the encrypted backup repositories. Credentials can be set but are never returned.
List storage destinations
List the team's storage destinations by name.
query Parameters
querySearch results by name.
per_pageNumber of results per page.
pagePage number to return.
statusOnly return destinations in this state: attention for destinations with servers still on previous credentials, in_use for destinations that hold a main or extra copy of a backup job, unused for the others.
List storage destinations › Responses
Paginated set of StorageDestination
Create a storage destination
Add an S3 or SFTP storage destination. Backup Chief first verifies it can list, read, write, and delete at the destination; nothing is saved when that fails. SFTP destinations created through the API sign in with a password; keys can only be generated in the Backup Chief app. The host keys the SFTP server presents at the first connection are pinned.
Create a storage destination › Request Body
nameDisplay name of the destination, unique within the team.
driverStorage driver. local is only available in development.
The settings of the driver; only the fields of the driver may be given. Fields left out keep their value on an existing destination of the same driver.
Create a storage destination › Responses
The storage destination was created.
Get a storage destination
Get one of the team's storage destinations with its settings and the jobs that use it. Credentials are never returned.
path Parameters
destinationGet a storage destination › Responses
StorageDestination
Update a storage destination
Rename a destination, rotate its credentials, or change its settings. Fields left out keep their value, credentials included. New credentials and settings are verified before they are saved.
Once a backup job stored a repository at the destination, its driver and location are fixed: only the name and credentials can change. New credentials reach the agents with their next configuration; keep the old credentials valid at the provider until servers_on_previous_credentials is 0.
path Parameters
destinationUpdate a storage destination › Request Body
nameDisplay name of the destination, unique within the team.
driverStorage driver. local is only available in development.
The settings of the driver; only the fields of the driver may be given. Fields left out keep their value on an existing destination of the same driver.
Update a storage destination › Responses
StorageDestination