All assets are publicly available and not secured. But the IDs are randomly generated as 128 bit number (GUID) and almost impossible to find out by just trial and error. Consider your assets safe.
You can download and link assets from the following URL:
So in case you are using the API you have to use:
Typically an asset URL will look like this:
In case your assets have a slug you can also use it for your URL:
If multiple assets with the slug exist it will return the first asset with this value.
The more parameter can be used to add additional text to the URL to improve your link quality:
The API reference with all parameters is provided here: https://cloud.squidex.io/api/docs#operation/AssetContent_GetAssetContent
The API provides several parameters to provide and manipulate images. Resized images are cached permanently to improve the performance for the next requests.
Use the following query string parameters:
The target width of the asset, if it is an image.
The target height of the asset, if it is an image.
The resize mode when the width and height is defined. Default:
You have to pass in either the
height parameter. if the asset is not an image these parameters have no effect.
Squidex supports the following resize modes:
Crops the resized image to fit the bounds of its container. If the desired width and height is greater than the image dimensions it behaves like
Crops the resized image to fit the bounds of its container, also desired width and height is greater than the image dimensions.
Pads the resized image to fit the bounds of its container. If only one dimension is passed, will maintain the original aspect ratio.
Pads the image to fit the bound of the container without resizing the original source. When downscaling, performs the same functionality as
Constrains the resized image to fit the bounds of its container maintaining the original aspect ratio.
Resizes the image until the shortest side reaches the set given dimension. Up-scaling is disabled in this mode and the original image will be returned if attempted.
You can also add the
quality parameter to the asset URL to define the quality from 0 (lowest) to 100 (best). If you define the quality the image will always be returned as jpeg format and you might loose transparency information.
Squidex provides the
ETag header for each asset. The browser caches the asset, along with its ETag. If the user wants retrieve the same URL resource again, it will first determine whether the locally cached version of the URL has expired (through the
Cache-Control and the
If the URL has not expired, it will retrieve the locally cached resource. If it is determined that the URL has expired (is stale), the client will contact the server and send its previously-saved copy of the ETag along with the request in an
Squidex now compares the passed ETag with the ETag of the current version of the asset. If the ETag values match, meaning that the asset has not changed, the server sends back an empty response with a HTTP 304 Not Modified status and the Browser will show the cached version.
More about the ETag header at Wikipedia.
You can add the
cache query parameter as a number of seconds to cache the image in the Browser.
Then the following header is added to the response:
If you have update the asset with a new version of the file you can retrieve old versions of the file by adding the version header. The first version has value
By default, Squidex provides the file name of the asset in the response. Therefore most browsers will download the file, which might be not desired for images. By setting this parameter to
When you have content items with asset fields, the assets are added as IDs to content item. Therefore by default you will only retrieve the IDs when you query content items and you have to do additional requests to get asset information.
You have two options to solve this:
With GraphQL you can get exactly the information you are looking for. You have to define the fields you want to retrieve, also from referenced assets or referenced contents. In the following example I have built a query to retrieve the testimonials with the associated company logo the fields I am interested for.
When using the normal REST endpoint you can use the
X-Resolve-Urls to define the fields that should be resolved. The value of this header must be a comma-separated list of field names: