Configure image variant priority in API response

albert__

Hello,

I would like to know if there is a way in Dédalo to configure image preferences in the API response.

Currently, the API always returns image URLs with the 1.5MB variant, for example:

/dedalo6/media/image/1.5MB/36000/rsc29_rsc170_36382.jpg

Our client requires the following priority order when displaying images:

1: modified (if available)
2: original

We can replace 1.5MB in the URL with modified or original. However, there is no way to determine whether those variants actually exist without making additional requests.

With the current API behavior, implementing this fallback logic on the client side would require validating each possible URL, which is not feasible in terms of performance and complexity.

Is it possible to modify the API so it returns the best available variant based on a defined priority, or that it provides the necessary data indicating which image variants exists for each asset? This would allow us to display the correct image without relying on trial and error requests.

Thank you in advance.

PaCo

Hi albert__

Yes, you can get the full component data setting v5 properties as:

{
  "data_to_be_used":"dato"
}

E.g. result:

[
  {
    "files_info": [
      {
        "quality": "original",
        "extension": "jpg",
        "file_name": "rsc29_rsc170_1.jpg",
        "file_path": "/image/original/0/rsc29_rsc170_1.jpg",
        "file_size": 1633774,
        "file_time": {
          "day": 2,
          "hour": 13,
          "time": 65120074460,
          "year": 2026,
          "month": 2,
          "minute": 34,
          "second": 20,
          "timestamp": "2026-02-02 13:34:20"
        },
        "file_exist": true
      },
      {
        "quality": "modified",
        "extension": "jpg",
        "file_name": "rsc29_rsc170_1.jpg",
        "file_path": "/image/modified/0/rsc29_rsc170_1.jpg",
        "file_size": 130797,
        "file_time": {
          "day": 2,
          "hour": 13,
          "time": 65120074203,
          "year": 2026,
          "month": 2,
          "minute": 30,
          "second": 3,
          "timestamp": "2026-02-02 13:30:03"
        },
        "file_exist": true
      },
      {
        "quality": "modified",
        "extension": "avif",
        "file_name": "rsc29_rsc170_1.avif",
        "file_path": "/image/modified/0/rsc29_rsc170_1.avif",
        "file_size": 12684,
        "file_time": {
          "day": 2,
          "hour": 13,
          "time": 65120074203,
          "year": 2026,
          "month": 2,
          "minute": 30,
          "second": 3,
          "timestamp": "2026-02-02 13:30:03"
        },
        "file_exist": true
      },
      {
        "quality": "1.5MB",
        "extension": "jpg",
        "file_name": "rsc29_rsc170_1.jpg",
        "file_path": "/image/1.5MB/0/rsc29_rsc170_1.jpg",
        "file_size": 16625,
        "file_time": {
          "day": 2,
          "hour": 13,
          "time": 65120074203,
          "year": 2026,
          "month": 2,
          "minute": 30,
          "second": 3,
          "timestamp": "2026-02-02 13:30:03"
        },
        "file_exist": true
      },
      {
        "quality": "thumb",
        "extension": "jpg",
        "file_name": "rsc29_rsc170_1.jpg",
        "file_path": "/image/thumb/0/rsc29_rsc170_1.jpg",
        "file_size": 7944,
        "file_time": {
          "day": 24,
          "hour": 10,
          "time": 65127322561,
          "year": 2026,
          "month": 4,
          "minute": 56,
          "second": 1,
          "timestamp": "2026-04-24 10:56:01"
        },
        "file_exist": true
      }
    ],
    "modified_file_name": "raspa2.jpg",
    "original_file_name": "Tulips.jpg",
    "modified_upload_date": {
      "day": 17,
      "hour": 16,
      "time": 65067813497,
      "year": 2024,
      "month": 6,
      "minute": 38,
      "second": 17
    },
    "original_upload_date": {
      "day": 17,
      "hour": 16,
      "time": 65067813486,
      "year": 2024,
      "month": 6,
      "minute": 38,
      "second": 6
    },
    "modified_normalized_name": "rsc29_rsc170_1.jpg",
    "original_normalized_name": "rsc29_rsc170_1.jpg"
  }
]

Note:
The best option is probably to create a new column with your own top-level domain (TLD) to prevent overrides, and configure it as I mentioned before, leaving the 'rsc266' ('image') column untouched.

Alex

Sincerely, I believe using the data for diffusion is an arduous approach. It's unnecessary. Simply changing the image's path is straightforward, effective, and as diffusion is a copy of your work data, changes made to the media don't directly reflect in the diffusion data. Therefore, the "file_exists" property isn't safe in this scenario, forcing you to manually do it. This is essentially the same as checking the media as it is currently published.

My suggestion is to avoid that approach. Instead, use the current path and adjust the quality in real-time. This is straightforward and efficient. Additionally, you can check the fallback option in JavaScript, which is quick and requires minimal effort and resources.

Other ways to go:

Another point is change the general diffusion DEDALO_PUBLICATION_CLEAN_URL to true to remove the path and added it manually as you need.
Use the id of the image and create a image processor to resolve the the image as you need, look an example here.

Note: This last option might be implemented into the API, but not in version 6. However, it could be a good implementation in version 7. In version 7, diffusion will be rebuilt from scratch, and a new publication API 2.0 will be created.

Best