What the API unlocks

Read this if you are deciding whether to build on the Sliick Files API. It covers what the provider-agnostic surface makes possible before you get into the mechanics.

One API. Every storage backend. The bytes land wherever the org points storage - Salesforce Files, Sliick Cloud, the customer’s own S3 bucket, GCP, Azure, or SharePoint - and your code never changes. That single fact opens up patterns that used to mean a rewrite per backend:

• Write generated documents straight to the customer’s bucket. A nightly batch renders thousands of invoices, calls uploadFiles, and they land in the org’s S3/GCP/Azure/SharePoint - no provider-specific code, no Salesforce storage bill, exactly where compliance wants them.
• Push huge files server-side, no browser, no ceiling. Generate a 200MB export, drop it in Salesforce Files, and relocateFiles streams it to external storage asynchronously via multipart. The 4MB Apex wall is gone.
• Turn a portal page into branded file intake. A screen flow places the Sliick File Upload component on an Experience Cloud page; customer photos and documents fly browser-direct into the org’s bucket - thumbnails generated automatically, zero Salesforce storage consumed.
• Switch storage providers without touching a line of code. An org moves from Salesforce Files to its own bucket; the same API quietly routes new uploads to the new provider and relocates the existing files in bulk.
• Let admins build file workflows in clicks. Record-triggered flows rename and route inbound email attachments to the right parent record - point and click, no Apex, callout-free.
• Hand file operations to an AI agent. The invocable actions are exactly the shape agent platforms consume: “attach this signed contract to the opportunity” becomes configuration, not an engineering project.
• Build on it from another package - safely. A sibling package detects Sliick Files via Type.forName + getCapabilities and drives every operation through Callable, degrading gracefully when it is not installed. No hard dependency, no version lockstep.

The rest of this section is how to wire it up. Start with Setup.