Create a workspace object
post
/20260430/aiDataPlatforms/{aiDataPlatformId}/workspaces/{workspaceKey}/objects
Creates a workspace object. You can create a file or folder in the workspace.
Request
Path Parameters
-
aiDataPlatformId(required): string
The [OCID](/iaas/Content/General/Concepts/identifiers.htm) of the AI Data Platform (Data Lake) instance.
-
workspaceKey(required): string
The key of the Workspace
Query Parameters
-
objectDescription: string
The description of the workspace object
Header Parameters
-
is-overwrite: boolean
A boolean which decides if overwrite is allowedDefault Value:
false -
is-upload-file-base64-encoded: boolean
A flag to identify if the upload file is base64 encodedDefault Value:
false -
opc-request-id: string
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID. The only valid characters for request IDs are letters, numbers, underscore, and dash.
-
opc-retry-token: string
Minimum Length:
1Maximum Length:64A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of running that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and removed from the system, then a retry of the original creation request might be rejected. -
path(required): string
Minimum Length:
1Maximum Length:255The absolute path of the file or folder -
should-update-recent: boolean
A flag to identify if the recent list should be updated.Default Value:
false -
type: string
Minimum Length:
1Maximum Length:255The type of workspace object.
Details for the new workspace object.
Root Schema : schema
Type:
string(binary)Response
Supported Media Types
- application/x-yaml
200 Response
Successful operation. The workspace object is created.
Headers
-
content-location: string(uri-reference)
Same as location.
-
etag: string
For optimistic concurrency control. See `if-match`.
-
location: string(uri-reference)
URL for the created workspace object. The workspace object key is generated after this request is sent.
-
object-key: string
Unique key of the object.
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
-
path: string
The full path of the object.
-
time-updated: string(date-time)
The date and time when Workspace Object was updated, in the format defined by RFC 3339. Example: `2016-08-25T21:10:29.600Z`
-
type: string
Type of the object
Root Schema : schema
Type:
string(binary)400 Response
Bad Request (invalid query parameters, malformed headers, and so on).
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
401 Response
Unauthorized (missing or expired credentials, and so on).
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
404 Response
Not Found. The requested resource was not found.
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
409 Response
Conflict. Request conflicts with the current state of the resource.
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
429 Response
Too Many Requests. Too many requests sent to the server in a short period.
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
500 Response
Internal Server Error. The server encountered an unexpected condition preventing fulfilment of the request.
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.
Default Response
Unknown Error. Error is not recognized by the system.
Headers
-
opc-request-id: string
Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Root Schema : Error
Type:
objectError information.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing.
-
message(required):
string
A human-readable error message.