Skip to main content
Everabyte developer platform Everabyte developer platform Everabyte gives your application a company-scoped storage layer: encrypted files, folders, buckets, versions, retention, and restore — managed through one REST API. Use the API when you need to automate uploads, build a document workflow, connect a backup process, or give your own customers a storage experience without operating object storage yourself.

Get Started

Follow the quickstart

Explore API Reference

Open the reference

​
Start with a guided path

Authentication

Upload & download

Organize content

Integrations

Security architecture

Errors & limits

​
How development usually flows

1

Create a company workspace

The developer REST API is company-scoped. Sign in to the Everabyte dashboard with a company account, then confirm billing and email verification where your plan requires it.Individual EverSpark accounts cannot use the developer REST API. They receive 403 API_COMPANY_ONLY. The one first-party exception is a key bound to an enrolled backup device.
2

Issue an API key

Create a key in the dashboard, choose the narrowest scopes that work, and store the secret in your server’s secret manager. The secret is shown only at creation time.
3

Call the REST API

Send X-Public-Key and X-Secret-Key on every request to https://api.everabyte.io/api. Start with reads, then add writes.
4

Handle lifecycle events explicitly

Files move through upload, versioning, trash, restore, and retention. Build these states into your application instead of assuming a file can always be deleted or overwritten.

​
What this documentation covers

The API reference publishes endpoints that are reachable with API-key credentials and verified against the backend route and permission model. Endpoints that exist but are session-only, administrative, reseller-provisioning, or still stabilizing are intentionally not published here.
Code samples are examples for common languages, not official SDKs. Response bodies in this documentation are illustrative, sanitized examples — not captured production traffic. Replace every placeholder credential before running anything.

​
Security, stated plainly

Everabyte uses a layered encryption architecture: files are encrypted by the application services before they are written to storage, and Everabyte’s storage infrastructure applies an additional, independent layer of encryption at rest. Decryption is governed by account-owner authorization: no Everabyte service uses a decryption key, or accesses decrypted content, outside an authorized operation. Read Encryption architecture for the full model, including key custody and the protections it does and does not provide.