Skip to main content
POST
Create

Authorizations

Authorization
string
header
required

The Authorization header expects a Bearer token.

Body

application/json
clusterId
string
required

ID of the PostgreSQL cluster that holds backup.

Response

200 - application/json

A successful response.

createdAt
string<date-time>

Creation timestamp.

createdBy
string

ID of the user or service account who initiated the operation.

description
string

Human readable description of the operation. 0-256 characters long.

finishedAt
string<date-time>

The time when the operation finished.

id
string

ID of the operation.

progressData
object

Any contains an arbitrary serialized protocol buffer message along with a URL that describes the type of the serialized message

request
object

Any contains an arbitrary serialized protocol buffer message along with a URL that describes the type of the serialized message

requestHeaders
The request headers that are essential for the request that generated the operation. For instance, `x-resetmask`. Without these headers the request might have been processed differently if repeated. All the header names *must* be converted to lower case. Validator is based on: https://httpwg.org/specs/rfc9110.html#considerations.for.new.field.names · object
resource
object

Any contains an arbitrary serialized protocol buffer message along with a URL that describes the type of the serialized message

resourceId
string

ID of the resource that this operation creates, updates, deletes or otherwise changes.

If the operation affects multiple resources or does not affect any API resources at all (e.g. a routine maintenance operation visible to the user), the [resource_id] must be empty.

status
object

The Status type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. Each Status message contains three pieces of data: error code, error message, and error details.

You can find out more about this error model and how to work with it in the API Design Guide.