Uploads API · org-scoped keys · JS & .NET SDKs

File uploads for your apps

OleqFiles gives your backend a simple API for apps, files, and presigned uploads. Authenticate with an organization API key — same REST surface in JavaScript and .NET.

Get startedHTTP APIPortal
OLEQFILES_API_KEYuploadspi.oleq.appsandbox · production apps

API keys

Organization-scoped secrets. Bind to roles and optional app scope — never expose them in the browser.

Apps & files

Each app is a file container. Uploads return an id and a public CDN URL after you complete the presign flow.

Presigned uploads

Presign, PUT to S3, then complete. The SDK upload helper runs that sequence; raw HTTP works too.

How it works

Three steps from zero to a stored file.

  1. 1

    Create an API key

    Sign in to the portal and create a key for your organization.

  2. 2

    Create an app

    Apps group uploads (slug + name). Create one in the portal or via the SDK before uploading.

  3. 3

    Upload a file

    Call files.upload in your SDK, or presign → PUT → complete over HTTP. Store the returned file id.

Choose your stack

Same API — pick the client that fits your runtime.

JavaScript / TypeScript

@oleq-ai/file-manager — Node, NestJS, Next.js server routes.

.NET

OleqAI.FileManager on NuGet — ASP.NET Core, workers, and services.

Guides

Concepts, auth, and REST details.

AuthenticationHeaders, org binding, and sandbox vs productionConceptsOrgs, apps, files, and where keys liveHTTP APIREST endpoints without an SDKIntroductionOverview and package links