API & developers

Getting an API key

Authentication uses API tokens. You can acquire a token via the /auth/login endpoint or from your account settings page on the Rediafile website.

POST /auth/login
Content-Type: application/json

{
  "email": "your@email.com",
  "password": "your_password"
}

The response will include your access token:

{
  "token": "eyJhbGciOiJIUzI1NiIs...",
  "expires_at": "2026-08-09T22:34:00Z"
}

Upload a file

Use the POST /files/upload endpoint with multipart/form-data:

curl -X POST https://api.rediafile.com/files/upload \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -F "file=@document.pdf" \
  -F "name=document.pdf" \
  -F "expires=30"

Parameters:

• file — The file to upload (required)
• name — Custom filename (optional)
• expires — Days until expiration (optional, default 7)
• password — Password protection (optional)
• folder_id — Target folder (optional)

Chunked uploads

For files larger than 100 MB, use chunked uploads. Send parts up to 100 MB each, get a session ID, and resume if the connection drops:

POST /files/upload/chunk
Headers:
  Authorization: Bearer TOKEN
  X-Upload-Session: SESSION_ID
  Content-Range: bytes 0-104857599/524288000

# Initiate session first
POST /files/upload/chunk/init
Body: { "filename": "large.zip", "size": 524288000 }

Event logs

Upload and retrieve event logs via the API for audit trails and compliance:

GET /logs?from=2025-01-01&to=2025-12-31&source=app-server
GET /logs/{id}

# Filter by date, source, or event type
GET /logs?limit=50&offset=0&event=download

API stability

The API will evolve over time as new endpoints are added. However, none of the current endpoints or response values will change. You can write your integration code knowing that it will not be affected by future updates. We follow semantic versioning for breaking changes.

Developer resources