|Required for:||iOS Android|
The CreateChildFile operation creates a new file in the provided container. The resulting file must be zero bytes in length.
The CreateChildFile operation has two distinct modes: specific and suggested. The primary difference between the two modes is whether the WOPI client expects the host to use the file name provided exactly (specific mode) or if the host can adjust the file name in order to make the request succeed (suggested mode).
Hosts can determine the mode of the operation based on which of the mutually exclusive X-WOPI-RelativeTarget (indicates specific mode) or X-WOPI-SuggestedTarget (indicates suggested mode) request headers is used. The expected behavior for each mode is described in detail below.
Note that a file matching the target name might be locked, and in specific mode, the host must respond with a 409 Conflict and include a X-WOPI-Lock response header as described below.
- container_id (string) – A string that specifies a container ID of a container managed by host. This string must be URL safe.
- access_token (string) – An access token that the host will use to determine whether the request is authorized.
- X-WOPI-Override – The string
- X-WOPI-SuggestedTarget –
A UTF-7 encoded string specifying either a file extension or a full file name, including the file extension. Hosts can differentiate between full file names and extensions as follows:
- If the string begins with a period (
.), it is a file extension.
- Otherwise, it is a full file name.
If only the extension is provided, the name of the initial file without extension should be combined with the extension to create the proposed name.
The response to a request including this header must never result in a 400 Bad Request or 409 Conflict. Rather, the host must modify the proposed name as needed to create a new file that is both legally named and does not overwrite any existing file, while preserving the file extension.
This header must be present if X-WOPI-RelativeTarget is not present; the two headers are mutually exclusive. If both headers are present the host should respond with a 501 Not Implemented.
- If the string begins with a period (
- X-WOPI-RelativeTarget –
A UTF-7 encoded string that specifies a full file name including the file extension. The host must not modify the name to fulfill the request.
If the specified name is illegal, the host must respond with a 400 Bad Request.
If a file with the specified name already exists, the host must respond with a 409 Conflict, unless the X-WOPI-OverwriteRelativeTarget request header is set to
true. When responding with a 409 Conflict for this reason, the host may include an X-WOPI-ValidRelativeTarget specifying a file name that is valid.
If the X-WOPI-OverwriteRelativeTarget request header is set to
trueand a file with the specified name already exists and is locked, the host must respond with a 409 Conflict and include an X-WOPI-Lock response header containing the value of the current lock on the file.
This header must be present if X-WOPI-SuggestedTarget is not present; the two headers are mutually exclusive. If both headers are present the host should respond with a 501 Not Implemented.
- X-WOPI-OverwriteRelativeTarget –
A Boolean value that specifies whether the host must overwrite the file name if it exists. The default value is
false. In other words, if X-WOPI-OverwriteRelativeTarget is not explicitly included on the request, hosts must behave as though its value is
This header is only valid if the X-WOPI-RelativeTarget is also included on the request. It must be ignored in all other cases.
If the user is not authorized to overwrite the target file, the host must respond with a 501 Not Implemented.
- X-WOPI-InvalidFileNameError – A string describing the reason the CreateChildFile operation could not be completed. This header should only be included when the response code is 400 Bad Request. This string is only used for logging purposes.
- X-WOPI-ValidRelativeTarget – A UTF-7 encoded string that specifies a full file name including the file extension. This header may be used when responding with a 409 Conflict because a file with the requested name already exists, or when responding with a 400 Bad Request because the requested name contained invalid characters. If this response header is included, the WOPI client should automatically retry the CreateChildFile operation using the contents of this header as the X-WOPI-RelativeTarget value and should not display an error message to the user.
The response to a CreateChildFile call is JSON (as specified in RFC 4627).
All optional values default to the following values based on their type:
|String||The empty string|
|Integer/Long||Varies; see individual properties for details|
No properties should be set to
null. If you do not wish to set a property, simply omit it from
the response and WOPI clients will use the default value.
Required response properties¶
The following properties must be present in all CreateChildFile responses:
- The string name of the file, including extension, without a path.
A string URI of the form
http://server/<...>/wopi/files/(file_id)?access_token=(access token), of the newly created file on the host. This URL is the WOPISrc for the new file with an access token appended. Or, stated differently, it is the URL to the host’s Files endpoint for the new file, along with an access token. A GET request to this URL will invoke the CheckFileInfo operation.
Optional response properties¶
- The HostViewUrl, as a string, for the newly created file. This should match the value returned in CheckFileInfo.