SteadyLink documentation
Host files behind links that never change. Upload once, replace the file whenever you need to, and every place that uses the link gets the new version.
SteadyLink gives every file one permanent address. When you publish a new version, the address stays the same and starts serving the new bytes. Websites, emails, QR codes, apps, and printed material keep working without anyone editing a link.
Start here#
Upload a file, copy its link, replace the file, and watch the link keep working. About five minutes.
The everyday workflow in the dashboard: batch uploads, scanning, and replacements.
Current and pinned revisions, caching, and what changes when you replace a file.
Every endpoint, with request and response examples in curl, JavaScript, and Python.
Build with SteadyLink#
Pick the tool that fits where your code runs. They all use the same API and the same scoped workspace keys.
@steadylink/sdk for Node.js, edge runtimes, and browsers.
steadylink on PyPI. Synchronous, no runtime dependencies.
Upload, replace, and print links from a terminal or CI job.
Publish release files from a workflow and keep their download links.
Use rclone, restic, Cyberduck, or the AWS CLI with your buckets.
Get signed events when revisions publish or scans finish.
The model in one minute#
- A workspace holds your buckets, members, API keys, usage, and settings.
- A bucket is a top-level container with its own defaults. Folders are paths inside it.
- A file (also called an asset) has one stable identity and one stable link:
https://cdn.steadylink.io/a/{asset_id}. - Each upload to that file creates a new revision. The link serves whichever clean revision is current, and you can roll back at any time.
- Every upload is scanned for malware. A file that fails the scan is blocked from delivery.
- Files are public or private. Private files are shared with expiring, revocable signed links.
Read Concepts for the details behind each of these.
Get help#
If something in these docs is wrong or missing, email [email protected] with the page URL. For API failures, include the X-Request-Id from the response so we can find the request in our logs. Current platform health is on the status page.