Restore a configuration backup - Fluid Topics - Latest

Fluid Topics API Reference Guide

Category
Reference Guides
Audience
public
Version
Latest

This web service restores a configuration backup onto the current portal.

  • This web service is available to users or API keys with the ADMIN role.
  • It is necessary to provide an Ft-Calling-App value when using Fluid Topics web services. See Fluid Topics calling app.
Method Endpoint
POST
/api/backups/{backupId}/restore
Path parameter Type Required? Description
backupId String Yes Unique identifier of the configuration backup to restore.
Use the List configuration backups web service to get the ID.

Request example

The following example shows a JSON request body for this web service:

{
  "subsets": [
    "SOURCES",
    "THEME",
    "LANGUAGES"
  ],
  "createAutoBackup": false
}
Field Type Required? Description
subsets Array No List of configuration categories to restore. If omitted, all available categories are restored. Possible values are: The following categories are not accessible from a CONSUMER portal: Some categories require others to be included in the same request:
createAutoBackup Boolean Yes If true, an automatic configuration backup of the current configuration is created before the restore is applied.

Response body

The following example shows a JSON response body for this web service:

{
  "id": "xyz789",
  "status": "IN_PROGRESS"
}
Field Type Description
id String Unique identifier of the restore operation.
Use this ID with the Get configuration restore status web service to track the progress of the restore operation.
status String Current status of the restore operation. Possible values are:
  • IN_PROGRESS
  • DONE
  • ERROR
Return code Description
200 OK The restore operation was created. Returns the operation ID and its initial status.
400 BAD REQUEST
  • The provided backupId does not exist.
  • The selected categories are invalid (unsupported on this portal type or missing dependencies).
  • A restore operation is already in progress
401 UNAUTHORIZED The authorization header is absent or invalid.
403 FORBIDDEN The user or API key must be an ADMIN.

For a comprehensive list of all possible return codes, see Return codes.