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
    • 11.14 Schreckhorn
    • Terminology
    • Solutions
    • User Guide - Deutsch
    • User Guide - English
    • 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
    • Fotoware 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
    • 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

JSON Data sent in webhook Example of the JSON data sent in webhook Webhook Payload for Asset Version Changes URLs with limited time validity
  • Home
  • Integrations and APIs
  • Integration using webhooks

Notifications when assets change in Fotoware

11. April 2025

Elaine Foley

Table of Contents

JSON Data sent in webhook Example of the JSON data sent in webhook Webhook Payload for Asset Version Changes URLs with limited time validity

You can use webhooks to configure the Fotoware system to send notifications when assets change in an archive.

  1. From the Tools menu (cogwheel icon), go to Site Configuration > Integrations.
  2. Select Webhooks. 
  3. Three asset events are available for notifications:
  • Asset ingested - Used to post a notification when an asset enters the system via the Fotoware API.

Note: Webhooks on asset ingestion are not supported if the upload destination is set to use a custom file system ingestion folder, since the uploaded asset may be picked up by, for example, a Color Factory server and transferred elsewhere and may not be indexed in Fotoware's asset storage folders.

  • Asset modified - Send a notification when an asset in the system changes.
  • Asset deleted - Send a notification when an asset is deleted by any means.

The asset data can be sent as Form or JSON data to the URL specified in the corresponding field.

JSON Data sent in webhook

Attribute Type Description
byline String The byline of the asset.
created ISO 8601 Date (String) Date when webhook was created.
data JSON object Asset representation.
description String Description of the asset.
file-size String Size of the file in bytes.
href String Original URL of the asset within the originating archive.
id String ID of the webhook.
pixel-height String A height of the image in pixels, e.g., "2560".
pixel-width String A width of the image in pixels, e.g., "1440".
preview-href String URL of the preview image.
tags String Tags (keywords) of the asset.
thumbnail-href URL (String) URL of the thumbnail.
title String Title of the asset.
type String Type of the data. In this case, "asset".

Example of the JSON data sent in webhook

Note that the data field below contains the Asset representation. Because of its size, it has been left out in the example.

JSON

{

"pixel-width": "2976",

"byline": "",

"description": "Some long description line",

"tags": "",

"file-size": "243340",

"title": "",

"thumbnail-href": "https://acme.fotoware.cloud/fotoweb/cache/5473/like/IMG_20190223_135249.t5c80f612.m200.x0UnqgdCS.jpg",

"created": "2019-03-07T11:44:27.802Z",

"href": "https://acme.fotoware.cloud/fotoweb/archives/5473-SummitPhotos/like/IMG_20190223_135249.jpg.info",

"data": {...},

"preview-href": "https://acme.fotoware.cloud/fotoweb/cache/5473/like/IMG_20190223_135249.t5c80f612.m800.xYQhD8Ty-.jpg",

"type": "asset",

"pixel-height": "3968",

"id": "12489453-7e9d-4604-af89-99b8f91db6a3"

}

Webhook Payload for Asset Version Changes

With versioning in Fotoware, the payload of the "asset modified" webhook has been updated to include information about how the asset was updated.

Metadata updates

1

2

3

4

5

6

7

8

9

{

...

"operation-name" : "updateMetadata",

"data": {

"asset: {<ASSET AFTER CHANGE, same as old "data">},

"assetBefore": {...},

"metadataDiff": {...}

}

}

Rename operations

1

2

3

4

5

6

7

8

{

...

"operation-name" : "rename",

"previous-name" : "oldName"

"data": {

"asset: {<ASSET AFTER CHANGE, same as old "data">}

}

}

 Restore revision

1

2

3

4

5

6
7

8

{

...

"operation-name" : "restoreRevision",

"data": {

"asset: {<ASSET AFTER CHANGE, same as old "data">},

"revisionsDiff": {...}

}

}

Upload of new local version (image data and potentially metadata) that is added to an asset's version history

1

2

3

4
5

6

7

8

9

{

...

"operation-name" : "upload",

"data": {

"asset: {<ASSET AFTER CHANGE, same as old "data">},

"assetBefore": {...},

"metadataDiff": {...}

}

}

URLs with limited time validity

Thumbnail and preview URLs have a limited lifetime. They are only valid for being consumed immediately, such as by downloading the rendition image immediately or by embedding it into a dynamic web page that is presented to a user agent immediately.

We do not recommend storing thumbnail and preview URLs for a longer time in external systems, as they will eventually expire. The expiration time of previews and thumbnails is unspecified, but the link should be valid for at least several seconds after it was received from an API request or webhook.

If an integration needs access to previews and thumbnails at a later time, we recommend storing the asset's API URL (data.href) and requesting thumbnails and previews through the API when needed. Alternatively, an integration can download the thumbnail or preview image and store them for later use

Was this article helpful?

Yes
No
Give feedback about this article

How can we improve this article?

Share additional info and suggestions

Related Articles

  • Application registration using OAuth 2.0
  • Get started with OAuth
  • Refreshing tokens
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

Definition by