Skip to main content

​
What the playground does

The API reference shows each operation’s path, parameters, required scopes, and an example request. Examples are copyable so you can adapt them in your own terminal or code.

​
What it deliberately does not do

This is a deliberate configuration, not a limitation of the documentation tooling.

​
Why live requests are disabled

  1. Production safety. Most operations mutate real data. A one-click delete or hard delete in a documentation page is a foot-gun, not a feature.
  2. Credential safety. These endpoints require a secret key. Sending it from a documentation page means the secret exists in a browser tab and potentially in a proxy.
  3. CORS. API-key headers are not allowed by CORS, so a browser request would fail preflight anyway.
  4. No auth proxy. Routing your secret through a documentation proxy moves the trust boundary without a security review.
Try requests from a terminal, or from a scratch environment where a mistake cannot destroy real data. Use a key restricted to a disposable bucket.

​
Safe way to experiment

  1. Create a dedicated bucket named for experimentation.
  2. Create a key with buckets:read, buckets:write, files:read, files:write, folders:read, folders:write.
  3. Restrict that key to the experiment bucket.
  4. Export credentials as environment variables.
  5. Run the examples from the reference.
Never place real values in a shell history you share. Use a secret manager in real deployments.

​
Example: read-only smoke test

Expected: a number. If you get 403, read the code.

​
Example: list a bucket’s files

​
Destructive operations

Delete, hard delete, and version deletion are documented for completeness. Do not run them against a bucket that holds data you need. If you must test them:
  1. Upload a file you can discard.
  2. Record its fileId.
  3. Soft delete it and restore it.
  4. Only then consider a hard delete, on the disposable file.

​
About the examples

Examples across this site are illustrative. They use placeholder identifiers and omit retries, structured error decoding, and secret management for brevity. They are examples, not official SDKs. There is no official Everabyte SDK documented at this time.

Quickstart

A guided first request.

API keys

Create a scoped experiment key.

Conventions

Envelopes and headers.

Errors

Interpreting failures.