Hi Miro Community,

I'm working on a project that uses the Miro REST API to update an existing image widget with content from a Dropbox URL. While the API successfully processes the updates (I get a 200 response and the modifiedAt timestamp confirms the widget has been updated), the widget still displays a cached version of the image hosted on Miro’s servers.

Here’s a summary of what I’ve done:

1. I’m appending a cache-busting query parameter (e.g., &cb=<timestamp>) to the Dropbox URL to ensure the URL looks unique for each update.
2. I’m temporarily setting the widget’s image URL to a placeholder before applying the updated Dropbox URL to force Miro to refresh the image.
3. The modifiedAt field in the widget API response updates, confirming that Miro acknowledges the change, but the imageUrl field still points to a Miro-hosted cached version of the image.
4. If I manually update the image widget in the Miro UI, it correctly fetches the updated Dropbox content.

My Questions:

1. Is there a way to ensure Miro fetches and displays the latest version of the image via the API, without manual intervention?
2. Does Miro ignore query parameters (like the cache-busting parameter) when determining whether to re-fetch an image from an external URL?
3. Are there specific best practices for API-driven updates to image widgets to avoid this caching behavior?

Any insights or suggestions would be greatly appreciated! Thank you in advance for your help!