Copy file to remote storage
Authentication
Every request made to https://api.uploadcare.com/ MUST be signed. HTTPS SHOULD be used with any authorization scheme.
Requests MUST contain the Authorization header defining auth-scheme and auth-param: Authorization: auth-scheme auth-param.
Every request MUST contain the Accept header identifying the REST API version: Accept: application/vnd.uploadcare-v0.7+json.
There are two available authorization schemes:
- For production:
Uploadcare, a scheme where asignature, not your Secret API Key MUST be specified. Signatures SHOULD be generated on backend. - For quick tests:
Uploadcare.Simple, a simple scheme where your Secret API Key MUST be specified in every request’sauth-param.
Headers
Request
MUST be either true or false. The true value makes copied files available via public links, false does the opposite.
The parameter is used to specify file names Uploadcare passes to the S3 bucket. If the parameter is omitted, your S3 bucket pattern is used. Use any combination of allowed values.
Parameter values:
${default}=${uuid}/${auto_filename}${auto_filename}=${filename}${effects}${ext}${effects}= processing operations put into a CDN URL${filename}= original filename without extension${uuid}= file UUID${ext}= file extension, including period, e.g. .jpg
Response
Destination file with that name already exists. Check the pattern parameter.