Upload a file to a LoRAAdapter

Uploads a single file to the LoRAAdapter's storage directory in
SeaweedFS, scoped to the base ModelClass the adapter targets. The front
proxy routes the request based on the x-upload-target header.

To upload an entire adapter directory (config + weight shards), call
this endpoint once per file, preserving the relative path in
{filePath}.

After all files are uploaded, the LoRAAdapter controller verifies file
presence and updates status accordingly.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

Kubernetes namespace of the resource.

string
required

Name of the base ModelClass the LoRA adapter targets. The front proxy
uses this segment to route the upload to the correct storage prefix.

string
required

Name of the resource.

string
required

Remote file path within the artifact's storage directory. When uploading
a directory tree, this preserves the relative path structure (e.g.
subdir/data.parquet). May contain forward slashes for nested paths;
the Envoy front proxy handles the full path via regex routing.

Body Params

Single-file upload as multipart/form-data. The file part carries the
raw file content.

file
required

The file content to upload.

Headers
string
enum
required

Must be set to loraadapters for LoRA adapter file uploads.

Allowed:
string

Hex-encoded MD5 digest of the file being uploaded. When provided, the
server verifies the uploaded file's integrity against this value during
upload. For Model and Dataset uploads, corresponds to the
spec.integrity.md5 field on the resource.

Responses
200

File uploaded successfully.

201

File created successfully.

401

Unauthorized — no or invalid bearer token provided.

403

Forbidden — the authenticated principal lacks permission.

404

Not Found — the resource does not exist.

Language
Credentials
Bearer
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here!