Keeping Content Up To Date

Any integration with Aprimo will likely require the ability to keep content up to date; whether this is updating content in Aprimo or updating content outside of Aprimo there are a few ways to tackle this use case. If your integration needs to update content within Aprimo the Aprimo REST API will be the recommended option. To update content outside of Aprimo making use of Aprimo DAM rules is the best option. These rules follow a set of configurable conditions, and when those conditions are met then actions will occur, such as sending an HTTP request to an integration with data.

Refer to the Keeping Content Up To Date folder in the POSTMAN collection for examples relevant to this use case.

If your integration needs to update Aprimo records, classifications, files, or other objects the Aprimo REST API will be what your integration uses. A common use is a CMS integration that sends updates to the Aprimo asset’s metadata containing usage stats about the asset or the specific pages that the asset is used on. Examples of updating Aprimo records can be found in the POSTMAN collection.

If the integration needs to update content outside of Aprimo then making use of Aprimo DAM rules is the recommended solution. This is common if the integration is connecting to any system that may also display metadata alongside an asset, such as an alt text field. CMS, Rights Management, PIM, and many others are examples of these systems. Aprimo DAM rules allow for conditions to be configured and, once those conditions are met, actions such as HTTP requests to occur that can send data to an integration to be used in updates.