Cloud Storage HTTP API Overview
CloudBase Cloud Storage offers two sets of HTTP APIs targeting different environment types. Pick the one that matches your environment.
Two cloud storage HTTP APIs
| Dimension | Classic Cloud Storage | PG Cloud Storage |
|---|---|---|
| Applicable environment | Classic environments (default) | PG environments |
| Authentication | TCB AccessToken (Authorization: Bearer <token>) | JWT Bearer Token (service_role / authenticated / anon) |
| Upload path | Client SDK gets a signature and uploads directly to COS | Goes through Storage API → COS; metadata is coordinated transactionally |
| Permission model | Bucket-level built-in permissions + JSON security rules | PostgreSQL RLS policies (SQL) |
| API surface | Basic object upload / download / delete / copy | Full Bucket / Object CRUD, signed URLs, object metadata, multipart upload |
How to choose
- Classic environments → Classic Cloud Storage HTTP API
- PG environments → PG Cloud Storage HTTP API
- Not sure which environment you're on → Check the environment overview in the CloudBase Console, or read the PG mode overview
Product docs
If you want to understand the full capabilities of cloud storage (console, SDK, CLI, cosBrowser, etc.) — not just the HTTP API:
- Cloud Storage product docs — root entry, with comparison and management options for both modes
- Classic Cloud Storage — SDK / console / CDN / Cloud Infinite, etc.
- PG Cloud Storage — RLS permission model and policy patterns