Z1 Object Gateway S3 API
Z1 supports a RESTful API that is compatible with the basic data access model of the Amazon S3 API.
Last verified by live API testing against s3.z1storage.com on 23 July 2026. The API is served over TLS only — plaintext HTTP is not available, and TLS 1.0/1.1 connections are rejected (modern clients negotiate TLS 1.3).
Features Support
The following table describes the support status for current Amazon S3 functional features:
| Feature | Status | Remarks |
|---|---|---|
| List Buckets | Supported | |
| Delete Bucket | Supported | |
| Create Bucket | Supported | Different set of canned ACLs |
| Bucket Lifecycle | Supported | |
| Policy (Buckets, Objects) | Supported | ACLs & bucket policies are supported |
| Bucket Website | Supported | |
| Bucket ACLs (Get, Put) | Supported | Different set of canned ACLs |
| Bucket Location | Supported | |
| Bucket Notification | Supported | |
| Bucket Object Versions | Supported | |
| Get Bucket Info (HEAD) | Supported | |
| Bucket Request Payment | Supported | |
| Put Object | Supported | |
| Delete Object | Supported | |
| Get Object | Supported | |
| Object ACLs (Get, Put) | Supported | |
| Get Object Info (HEAD) | Supported | |
| POST Object | Supported | |
| Copy Object | Supported | |
| Multipart Uploads | Supported | |
| Object Tagging | Supported | |
| Bucket Tagging | Supported | |
| Storage Class | Supported | |
| Object Versioning (per-version GET/HEAD/DELETE, ListObjectVersions) | Supported | Every PUT returns a unique x-amz-version-id |
| S3 Object Lock — Governance mode | Supported | Deletion of locked versions requires the x-amz-bypass-governance-retention header — AWS-identical semantics |
| S3 Object Lock — Compliance mode | Supported | True WORM: no credential can delete or shorten a locked version before its retain-until date |
| Default bucket retention (PutObjectLockConfiguration) | Supported | Applied automatically to every new object — ideal for backup buckets |
| Per-version retention queries (GetObjectRetention with versionId) | Supported | HEAD responses include lock mode, retain-until and version-id |
| Bucket Policies (Put/Get/Delete) | Supported | |
| Server-Side Encryption (SSE-S3, SSE-KMS, SSE-C) | Not available | Use client-side encryption (native in Veeam, Duplicati, Duplicacy, MSP360 and similar tools) |
Unsupported Header Fields
The following common request header fields are not supported:
| Name | Type |
|---|---|
| Server | Response |
| x-amz-id-2 | Response |
Update (23 July 2026): x-amz-version-id and x-amz-delete-marker are now fully supported and no longer appear in the list above. Every PUT returns a unique version-id, per-version GET/HEAD/DELETE and ListObjectVersions are functional, and deleting a versioned object without a version-id correctly adds a delete marker while retaining the data version. This supersedes earlier revisions of this page.