Request Signed URL for Upload/Download Files
to generate signed URLs both for uploads and downloads
Last updated
Was this helpful?
to generate signed URLs both for uploads and downloads
Last updated
Was this helpful?
POST <base_url>/port/api/v1/commerce/signedUrls
Please replace <base_url> as explained .
Our system currently only support file sizes with a maximum limit of strictly less than 2GB, or in other words:
This essentially implies that any user interaction with our API involving data transfer would necessitate adherence to this requirement. Manifestly, if a file size exceeds the defined threshold of 2GB, it may possibly impede the operation of the application.
File name
should not contain space.
should contain the file extension, including but not limited to .jpg, .png, .pdf, etc.
use a unique name for each file. Filename is unique perissuer-address otherwise it will fail.
This is to avoid modification of files that are already used in SRR.
However given the upgrade to the IPFS protocol, there is no need to be concerned for the filename in terms of its look. The filename is not going to exist in the minted SRR since it is going to be converted to IPFS and the filename will be replaced with cid that is a function of the file's content and not file's name.
*In order to make the file names unique anyway, you can prefix/suffix the name with a unique number such as Date.now() .
**Given the underlying usage of IPFS, there is no need to be worried about duplicated contents. Since if two files with different name but same content will eventually be replaced with the same ipfs url.
commerce-api-key*
string
Commerce API Key.
issuer-address*
string
Contract Address of API Key owner.
action*
string (write and read)
Field to specify the action of the Signed URL. Value
write
to request upload signed URL, and
read
to request download signed URL.
payload*
array
Array of signed URL request.
payload[*].filename*
string
If the client needs to delete an existing file, please contact Startbahn.
payload[*].category*
string
Use non_attachment_file to upload thumbnails and contract terms.
The API responds with 201 when the signed URL is created. The validity of the signed URL is 15 minutes after it is created.
The client’s back-end needs to consider its upload speed. If the files that need to be uploaded are many, client’s back-end may consider splitting the signed URL request to ensure that all of the files are uploaded.
results
results of the request
Array
results[*].filename
Name of the file, same as one in the request
string
results[*].contentType
Content-Type that was chosen and set for the file. You need to set the same value in Content-Type header when uploading or downloading the file with the signed URL. Otherwise, you will get an error about signature mismatch.
string
results[*].url
string
results[*].finalUrl
The URL that client should save and use when calling issue endpoint. Check below for details
string
artwork
On issue endpoint, use it for payload.attachmentFiles[*].url
certificate, installation, for_authenticity
On issue endpoint, use it for payload.attachmentFiles[*].url
non_attachment_file
use it for the field in metadata on the image, payload[*].metadata.thumbnailURL or payload[*].metadata.contractTerms.fileURL
The filename must meet the constraints mentioned .
Please refer to to understand the difference among the categories.
The signed URL that client can use to perform action such as upload or download. NOTE: This URL is only valid for 15 minutes and should not be saved. Please check the .
.
Check .
Check .
