SWS CDN – Developer Guide
SWS CDN stores your files and delivers them to your users. Your backend talks to the CDN with an API key. Your users never see that key: they get a presigned URL for private files, or a permanent public URL for public assets.
API base URL
https://api-gateway.opsfusioncloud.com/cdn-route· REST + JSON · SDKs v100.42.1 for .NET, Python and Node.js · Console: cdn.shorynow.com
1. Overview
How it fits together
| Role | |
|---|---|
| Browser / mobile app | Talks only to your own API. Never holds the API key. |
| Your backend | Holds the API key and calls the CDN API with the X-Api-Key header. |
| CDN API | Stores and serves the files. |
Which URL should I use?
| Situation | Use | Shape |
|---|---|---|
| Your backend needs the file | API route with X-Api-Key | /api/v1/files/{bucket}/{objectKey} |
| A user opens a private file in a browser or app | Presigned URL (expires) | /files/presigned/…?expires=…&sig=… |
| Anyone can see the file (logo, product image) | Public bucket URL (permanent) | /public/{bucket}/{objectKey} |