Route for uploading raw data to the desired folder of a bucket.
The POST body is saved as a file to the bucket. The path to the file is determined by the folder parameter with a Year/Month/Day component added. The actual filename is created from the current time HourMinuteSecond augmented by optional pre- and suffix.
The folder name inside the bucket, where the files will be stored
The prefix of the autogenerated file name. It will be ignored if the file name is defined in the Content-Disposition header.
The suffix of the autogenerated file name. It will be ignored if the file name is defined in the Content-Disposition header.
An optional header used to define the file name. Only the filname is used, the media type is ignored.
Note: The use if this header is uncommon and included for backward compatibility only. If you are tempted to use it, you might want to consider switching to the “Upload File” route.
Data to upload.
Upload was successful.
Route for returning the upload UI that will later send checked/verified files into the bucket.
Request was successful
Route for validating the file uploaded via the UI and uploading it to the desired folder if the option was selected and validation was successful.
The folder name inside the bucket, where the files will be stored
File to validate/upload.
Request was successful