Skip to main content
GET
Get S3-Compatible Credentials for Blob Storage
Returns S3-compatible credentials for tools such as aws-cli, rclone and boto3. The pair is derived from the API key that makes the call, so revoking that key cuts S3 access at once. With an API key that has only blob:read, the credentials are read-only (access.write is false). Treat secret_access_key as a password. This route requires an API key: a dashboard session is refused. Rotating the API key replaces the pair, so fetch the credentials again afterwards. Scope: blob:read.
string
The workspace ID, when the blob belongs to a workspace. The call acts on the blob of the workspace owner and needs the blob:read workspace permission (blob:manage on routes that change data). Leave it out to act on your own blob.

Example request

Response

object
The S3 credentials for the account.

Error Responses

string
The error code indicating the reason for failure. Possible values:
  • AUTH_TOKEN_MISSING (401): No Authorization header was sent.
  • API_KEY_INVALID (401): The API key doesn’t exist, was revoked, or its secret doesn’t match.
  • API_KEY_SCOPE_DENIED (403): The key lacks the scope this route needs (blob:read or blob:write); details.required names it.
  • WORKSPACE_PERMISSION_DENIED (403): Only with workspace_id: you’re not a member, or your role lacks the blob permission.
  • WORKSPACE_NOT_FOUND (404): Only with workspace_id: no workspace with that ID, or you’re not a member.
  • VALIDATION_ERROR (400): The call wasn’t made with an API key; details.reason is api_key_required.
  • RATE_LIMIT_EXCEEDED (429): More than 10 calls in one hour. details.retry_after gives the wait in seconds.