Authentication and URL format
The simple API is useful when an S3 SDK is unnecessary. Send the zone API key in the AccessKey header and put the zone name and object key in the URL.
- Endpoint format: https://storage.acdn.uz/{storageZoneName}/{objectKey}.
- The AccessKey value is different from the S3 access key ID and secret.
- For browser download links, accessKey may be passed in the query string because anchors cannot attach a header.
- The request body for PUT contains raw bytes, not JSON, base64, or multipart/form-data.
Supported operations
Download an object. A trailing slash or zone root returns a JSON directory listing.
Inspect an object or check a directory listing without a response body.
Create or replace one object from the raw request body.
Delete the exact object key. Directories are not deleted recursively.
cURL examples
curl --request PUT \
--url https://storage.acdn.uz/<bucket>/backups/archive.tar \
--header 'AccessKey: <api-key>' \
--header 'Content-Type: application/octet-stream' \
--data-binary '@/absolute/path/to/archive.tar'
curl --request GET \
--url https://storage.acdn.uz/<bucket>/backups/archive.tar \
--header 'AccessKey: <api-key>' \
--output archive.tar
curl --request DELETE \
--url https://storage.acdn.uz/<bucket>/backups/archive.tar \
--header 'AccessKey: <api-key>'
Responses and errors
- Successful PUT returns 201 Created; successful DELETE returns 200 OK.
- Listings use JSON. Object reads return the stored content type and bytes.
- Simple API errors are plain HTTP text responses. XML error documents are reserved for signed S3 requests.