FiloraFS-Lite API reference

Browser API testing

Run FiloraFS-Lite and open http://localhost:8080/api-test. The page uses the local demo API key and preserves the same access rules as direct API clients.

File endpoints

FiloraFS-Lite endpoints
Method	Path	Purpose
POST	/file	Upload a multipart file
GET	/file/{filename}	Stream a stored file
GET	/file/list	List stored filenames
GET	/file/info/{filename}	Read filesystem metadata
DELETE	/file/{filename}	Delete a stored file

POST/fileX-API-KEY

Upload one allowed multipart file to the configured local directory. The response is the generated stored filename.

Headers

X-API-KEY: <configured-key>
Content-Type: multipart/form-data

Parameters

file — required multipart file part

Successful response

"4d95df24-3ae8-4e7c-a598-7ae7f40b24cc.pdf"

Relevant errors

Unauthorized when the API key is missing or invalid.
Validation failure when the reported content type is not allowed.

cURL

curl -X POST http://localhost:8080/file \
  -H "X-API-KEY: <configured-key>" \
  -F "file=@architecture.pdf"

GET/file/listX-API-KEY

Return the stored filenames available in the configured local directory.

Headers

X-API-KEY: <configured-key>

Relevant errors

Unauthorized when the API key is missing or invalid.

Access model

Every non-OPTIONS request is checked by ApiKeyFilter. Lite has no users, roles, or ownership model.