/video/workspacesCreate a video workspace
Creates a video workspace that you can use to organize videos by team, department, or use case. Supply name and type, and include the storage configuration required for the selected workspace type. A 200 response returns the created workspace, including its ID and configuration.
- IdempotentThe SDK sends
Idempotency-Key, so a retried request is only applied once.
Video workspace configuration. name and type are required; storage configuration fields are required when they match the selected type.
This is a required field if workspace type is aws.
This is a required field if workspace type is azure.
This is a required field if workspace type is backblaze.
This is a required field if workspace type is cloudflare.
This is a required field if workspace type is cloudinary.
Data localization region
Gumlet provides the functionality of creating multiple video assets using the same set of parameters.
This is a required field if workspace type is dostorage.
This is a required field if workspace type is gcs.
The five to ten character unique identifier of the Gumlet Insight Property available on the dashboard.
This is a required field if workspace type is linode.
Specify a text string or identifier for the workspace.
This is a required field if workspace type is proxy.
Video workspaces are top-level entities in Gumlet. You can use them to organize videos for different teams/departments or use cases.
Gumlet provides multiple options for securing your video playback.
This is a required field if workspace type is wasabi.
This is a required field if workspace type is zoom.
Created at time in ISO 8601 format
Default profile for this workspace
List of folders inside this workspace
Workspace ID
Workspace name
Player configuration for this workspace
Workspace type
Updated at time in ISO 8601
One documented failure
parameter_missingOne or more required values are missing.
One documented failure
invalid_api_keyAPI key supplied with request is invalid
One documented failure
unauthorised_feature_accessYour plan doesn't have this feature, please upgrade your current plan to access this feature.
One documented failure
invalid_parameterbody must have required property '<field>'
name and type are required. Include the configuration object for the selected workspace type, with its required fields: for example, aws requires bucket_name, bucket_region, access_key, and secret, while azure requires azure_account_name, azure_container_name, azure_shared_token, and `azure_path. A 400 or 422 indicates an invalid or unprocessable request; a 401 indicates missing or invalid authentication, and a 403 indicates the feature is unavailable on your plan.