/content mapping & automation

Update a Collection via API

In this lesson, you’ll learn how to update collections connected to a site. We’ll walk through a real example: updating the FAQ section on a homepage by pointing the existing collection to a new dataset. Along the way, you’ll learn how to structure the API call, define critical fields like the page item URL, and ensure the data connection is valid. This process allows you to keep client content fresh and relevant—without needing to manually update items in the Duda editor.

API Reference

PUT https://api.duda.co/api/sites/multiscreen/{site_name}/collection/{current_collection_name}


Update an existing collection’s settings. Content items cannot be modified, added, or deleted with this endpoint.

Note: You only need to pass the data fields you want to update and do not need to send the entire data object representing the whole content library.

Documentation: Update Collection

Best Practice

By default, Duda caches external collection data for up to 2 hours to optimize site performance.

If you need to force a refresh—especially after updating your external source—you can use the Refresh Collection Data API endpoint.

This endpoint triggers an asynchronous fetch of the external data. If Duda detects any changes, it will:

  • Update the collection in its internal database
  • Clear the cache for all site pages using that data


Use this when you need your live site to reflect content changes immediately.

Note

The Update Collection API call is designed to update the metadata of an existing collection—such as swapping its data source URL or adjusting settings.


It does not:

  • Create new or update existing rows (items or objects) in the existing collection.
  • Create new or update existing fields (data keys or columns) in the existing collection.


To add new content or structure to your collection, use these dedicated endpoints: