Qodex.ai

Restores a key to a vault from a file.

POST {{managementEndpoint}}/20180608/keys/actions/restoreFromFile

Restores the specified key to the specified vault, based on information in the backup file provided. If the vault doesn't exist, the operation returns a response with a 404 HTTP status error code. You need to first restore the vault associated with the key.

HEADERS

KeyDatatypeRequiredDescription
content-lengthstring(Required) The content length of the body.
if-matchstringFor optimistic concurrency control. In the PUT or DELETE call for a
resource, set the if-match parameter to the value of the etag from a
previous GET or POST response for that resource. The resource will be
updated or deleted only if the etag you provide matches the resource's
current etag value.
content-md5stringThe base64-encoded MD5 hash value of the body, as described in RFC 2616, section 14.15.
If the Content-MD5 header is present, Key Management performs an integrity check on the body of the HTTP request by computing the MD5
hash for the body and comparing it to the MD5 hash supplied in the header. If the two hashes don't match, the object is rejected and
a response with 400 Unmatched Content MD5 error is returned, along with the message: "The computed MD5 of the request body (ACTUAL_MD5)
does not match the Content-MD5 header (HEADER_MD5)."
opc-request-idstringUnique identifier for the request. If provided, the returned request ID
will include this value. Otherwise, a random request ID will be
generated by the service.
opc-retry-tokenstringA token that uniquely identifies a request so it can be retried in case
of a timeout or server error without risk of executing that same action
again. Retry tokens expire after 24 hours, but can be invalidated
before then due to conflicting operations (e.g., if a resource has been
deleted and purged from the system, then a retry of the original
creation request may be rejected).
Content-Typestring
Acceptstring