HTTP (TUS) Source
Rilavek exclusively supports the TUS protocol for HTTP uploads to guarantee bulletproof resumption and reliable ingestion over flaky networks. We do not support legacy single-request HTTP POSTs.
Endpoint Structure
Your pipeline exposes a standard TUS endpoint. You must provide the correct pipe_id in the URL.
Authentication
TUS requests must be authenticated using a Bearer token provided in the Authorization header. You can generate these temporary upload tokens dynamically via our API.
Generating Tokens via API
Every Sender identity you create has an associated API Token starting with sk_. This token is a highly privileged, private secret, and you must use it to generate temporary upload tokens on behalf of that Sender.
curl -X POST https://rilavek.com/api/v1/tokens \
-H "Authorization: Bearer sk_YOUR_PRIVATE_SENDER_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"pipeId": "YOUR_PIPE_ID"
}'sk_ Sender API token in client-side code, mobile apps, or public repositories. It must be kept private on your backend server. You should only ever send the generated temporary (tmp_) tokens to the end client to perform the actual file upload.Client Integration
Avoid writing a custom TUS client unless absolutely necessary. We strongly recommend using standard, battle-tested libraries such as:
- Uppy (Browser / React / Vue) - Use the
@uppy/tusand@uppy/golden-retrieverplugins for the best experience. tus-js-client(Node.js / Browser)tus-py-client(Python)
Simply initialize the client and point the endpoint parameter to your generated upload URL.