Data Types


Request body for BeginMultipartUpload.

"mime": String,
"protocol": String,
"size": Integer,
"tags": String[]
"metadata": {
"myCustomField1": true,
"myCustomField2": {
"hello": "world"
"anotherCustomField": 42
"mime": "text/plain",
"originalFileName": "example.txt",
"path": {
"fileName": "example-{UNIQUE_DIGITS_4}{ORIGINAL_FILE_EXT}",
"folderPath": "/uploads"
"protocol": "1.1",
"size": 43182,
"tags": [

Arbitrary JSON to store against the file as metadata.

You can retrieve this later via a GetFileDetails request.

Type: FileMetadata

The file's MIME type.

Example: "text/plain"

Type: String

Min Length: 3

Max Length: 255

The file's original name on the user's device.

Example: "example.txt"

Type: String

Min Length: 1

Max Length: 255

The path to upload the file to.

Type: FilePathDefinition

Multipart upload protocol version to use.

The latest Bytescale SDKs use the latest supported version.

Recommended: "1.1"

Default: "1.0"

Type: String

Allowed Values: "1.0", "1.1"

The size of the file in bytes.

Example: 43182

Type: Integer

Minimum: 0

The file tags to store against the file.

When you associate file tags with a file, Bytescale checks which rules match the tags (if any) and applies those rules to the upload request:

Rules can include max file size checks, traffic limit checks, rate limit checks, and so forth. These are configured in the Bytescale Dashboard.

Example: ["example_tag"]

Type: String[]

Was this section helpful? Yes No

You are using an outdated browser.

This website requires a modern web browser -- the latest versions of these browsers are supported: