Skip to main content
Documentation & User Guides | FotoWare

Dynamic tags for User Interface Integrations

This topic lists dynamic tags that are supported in user interface integrations






File extension of the asset, not including the dot.




File name of the asset, not including the folder path



URL of the asset

The format of the URL is intentionally unspecified. No assumptions should be made about the format of URLs. URLs should not be parsed or generated by third-party applications.

The URL can be used by an API client to query the asset representation of the asset.

For more information, see The FotoWeb REST API.



Value of a metadata field of the asset.

If the metadata field was changed interactively by the user entering a new value in an interactive metadata editor as part of running the action, then this tag expands to the latest modified value.

If multiple metadata macros are run as part of the action, and they modify the same metadata field, then this tag expands to the value of the field after applying all of the previous metadata macros in the order in which they are defined in the action configuration.

This means that the order of metadata macros matters.

The FIELD parameter must be the numeric ID of the metadata field. For a reference of standard field numbers, see the FotoWare default field code reference topic.

If the user entered the value foo for field 5 in an interactive editor, then


if used in the first metadata macro expands to foo.

If the following metadata macro is used to set the value of field 120:

Title: {{asset.metadata:5}}

then in the next metadata macro, the tag


expands to:

Title: foo

Authentication of User Interface Integrations

A UII can obtain an access token by requiring the user to log in with OAuth from within the UII (as a regular web integration would do).

  • Was this article helpful?