Upload files

Upload files — the request-URL / commit flow.

Where: Files → Browser → Upload file · /projects/<project>/files/browser

In the dashboard, uploading is one action: press Upload file, pick a file, and it lands in the folder you are currently viewing (the button reads "Uploading…" while it works). Under the hood it is a three-step direct upload — the bytes go straight to your storage provider and never pass through Norbix.

Screenshot TODO — capture comes from testing-plan area 10-payments-files.

Step by step

1. Request an upload URL — the dashboard asks the API for a pre-signed PUT URL for the target path (current folder + file name) and content type. Endpoint: Request Upload Url.

2. PUT the bytes — the browser sends the file directly to the storage provider using that URL.

3. Commit — the dashboard calls Commit Upload with the path, file name, content type, and size. The backend records the file and raises the FileUploaded event, which runs any OnFileUploaded trigger. The browser list then refreshes.

Example: uploading invoice-4821.pdf while viewing invoices/2026 requests an upload URL for path invoices/2026/invoice-4821.pdf with content type application/pdf, then commits it with its size in bytes.

The same flow is what your own apps use — request the URL, PUT, commit — so files uploaded by end users appear in this browser too.

Use it from code

Request Upload Url · Commit Upload

API reference

Endpoints: Request Upload Url, Commit Upload.