Getting Started

Welcome to the Elept developer documentation. Our platform provides a simple REST API and secure dashboard for application uploads, Twilio recordings, static website asset hosting, and database archives.

The File UID Philosophy

Unlike raw S3 bucket integrations, your application database does not need to store absolute URLs, bucket names, or complex credentials. Instead, you upload files to Elept and store a simple string: the File UID (e.g. file_abc123) in your user database.

Whenever you need to serve the file to a client, query our API for a Signed URL or a CDN asset path. This keeps your application logic completely decoupled from the underlying storage cloud providers (R2, B2, or local).

Developer Integration Flow

1. Obtain API Key

2. Upload File (POST /api/v1/files)

Send a multipart HTTP POST containing your file. Elept returns a unique file UID (e.g. file_abc123).

3. Fetch Access Link (POST /api/v1/files/{uid}/signed-url)

Request a time-restricted signed link whenever an authenticated user attempts to view the file.

Quick Code Example (PHP)

// Request signed link from Elept API in PHP
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, "https://elept.com/api/v1/files/file_abc123/signed-url");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    "Authorization: Bearer el_live_key_...",
    "Content-Type: application/json"
]);
curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode([
    "purpose" => "view",
    "expires_in" => 3600
]));

$response = json_decode(curl_exec($ch), true);
$signedUrl = $response['data']['url'];

Next: API Authentication →