Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  1. Fotoware Alto
    • End-User Manual
    • User Guides
    • Solutions
    • Terminology
    • API Changelog
  2. Fotoware Veloz
    • Managing users and groups
    • Configuring archives
    • Configuring workflows
    • Configuring site behavior
    • Navigating and searching to find your assets
    • Working with your assets
    • Editing asset metadata
    • Uploading files
    • Version Control in Fotoware
    • Albums - Creating and sharing collections
    • Placing assets in a CMS
    • Working with the Fotoware Pro interface
    • Using the Fotoware plugins
    • Consent management
    • User guide to FotoWeb for iPad (Legacy)
    • Picture conferencing with FotoWeb Screens (Legacy)
    • What's what in Fotoware
    • GDPR
    • Fotoware Veloz releases
    • Activity Exports
    • Example workflows
  3. Fotostation
    • Getting started with Fotostation
    • Viewing, selecting and sorting files
    • Managing your assets with archives
    • Adding metadata to assets
    • Searching for assets
    • Working with your assets
    • Version Control in Fotostation
    • Automating tasks with Actions
    • Configuring metadata fields and editors
    • Configuring Fotostation
    • Configuring Fotostation for multi-user environments
    • Troubleshooting Fotostation
  4. Fotoware Flow
    • What is Flow?
    • Getting started
    • Flow dictionary
  5. Fotoware On-Premises
    • Getting started
    • Index Manager
    • FotoWeb
    • Color Factory
    • Connect
    • Operations Center Guide
  6. Integrations and APIs (Fotoware Veloz & On-Premises)
    • The Fotoware API
    • Creating integrations using embeddable widgets
    • Authorizing applications using OAuth
    • Auto-tagging
    • FotoWeb Drag and Drop export
    • Integration using webhooks
    • Optimizely and Episerver plugin documentation
    • User Interface Integrations
  7. Fotoware Mobile
    • User guide for Fotoware Mobile for iPhone and Android
    • User guide to FotoWeb for iPad (Legacy)
    • User guide to FotoWeb for iPhone and Android (Legacy)

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

Support

Table of Contents

Authentication of User Interface Integrations OAuth token notes
  • Home
  • Integrations and APIs (Fotoware Veloz & On-Premises)
  • User Interface Integrations

Dynamic tags for User Interface Integrations

17. June 2025

Elaine Foley

Table of Contents

Authentication of User Interface Integrations OAuth token notes

This topic lists dynamic tags that are supported in User Interface Integrations (UII).

Tag Description Examples

{{asset.ext}}

{{asset.extension}}

File extension of the asset, not including the dot.

jpg

{{asset.name}}

{{asset.filename}}

File name of the asset, not including the folder path

 

{{asset.href}}

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.

{{asset:FIELD}}

{{asset.metadata:FIELD}}

Value of a metadata field of the asset.

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 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 returns 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 returns 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.

The order of metadata macros matters when determining the final value for the asset metadata field tag.

For example, if the user entered the value foo for field 5 in an interactive editor, then {{asset.metadata:5}} would return foo if used in the first metadata macro.

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

{{asset.metadata:120}}

returns:

Title: foo

{{oauth.token}}

OAuth token that can be used by the UII to make requests to the Fotoware API on behalf of the user.

https://external.com/app/1?token={{oauth.token}} passes token as a query parameter to the server serving the UII (needed if API requests are made from the server).

https://external.com/app/2#token={{oauth.token}} passes token as fragment parameter to the UII (preferred if the server serving the UII does not need the access token, i.e. if API requests are made directly from JavaScript)

An access token is only available if the user is logged into FotoWeb. Otherwise, this tag resolves to an empty string.

Making API requests directly from JavaScript requires CORS to be enabled for the UII.

An alternative way for a UII to obtain an access token is to require the user to log in with OAuth from within the UII (as a regular web integration would do). By using {{oauth.token}}, this additional login is not necessary. The user only needs to be logged in to FotoWeb.

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).

OAuth token notes

Fotoware recommends using the token fragment whenever possible, especially if only the front-end of the integration uses the token.

If, however, the integration has a backend that uses the token, the query string must be used.

An alternative way for a UII to obtain an access token is to require the user to log in with OAuth from within the UII (as a regular web integration would do). By using {{oauth.token}}, this additional login is not necessary. The user only needs to be logged in to FotoWeb.

Specs on UII here: 

https://fotoware.atlassian.net/wiki/spaces/FOT/pages/617480240/User+Interface+Integrations#Obtaining-Access-Tokens

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • User Interface Integrations - an overview
  • Configuration
  • Uploading the active configuration to a server
eco-lighthouse-miljøfyrtårn

Company

  • About us
  • Resellers
  • Careers
  • Contact us

Help & support

  • Support center
  • Consultancy
  • Tech partners
  • Fotostation
  • System status

Trust Center

  • Legal
  • Security
  • Sustainability & ESG

Locations

Fotoware AS (HQ)
Tollbugata 35
0157 OSLO
Norway
FotoWare Switzerland AG
Industriestrasse 25
5033 Buchs (AG)
Switzerland

Copyright 2025 Fotoware All rights reserved.

  • Terms of service
  • Privacy policy
  • Cookie policy

Knowledge Base Software powered by Helpjuice

Expand