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

Programmatic export using the API API response Size and aspect ratio Example Getting the preset URL Notifications when exported assets change
  • Home
  • Integrations and APIs
  • The Fotoware API
  • Fotoware API Overview

Export API

04. April 2025

Elaine Foley

Table of Contents

Programmatic export using the API API response Size and aspect ratio Example Getting the preset URL Notifications when exported assets change

There are two ways of using CMS export in integrations:

  • Interactively - by embedding the CMS export widget into a third-party application
  • Automatically - by using the export API.

This article describes how to use the export API.

Programmatic export using the API

Using the export API assumes that all parameters for exporting an asset are either predefined or already known otherwise (for example, entered by a user through a custom interface in a third-party application). An asset can then be exported using the following request:

1

2

3

EXPORT /fotoweb/archives/5000-My%20Archive/Path/to/file.jpg.info

Content-Type: application/vnd.fotoware.export-request+json

Accept: application/vnd.fotoware.export-data+json

with request body:

1

2

3

4

5

6

{

"width": 1234 | 0,

"height": 1234 | 0,

"publication": "http://example.org",

"preset": "/fotoweb/me/presets/exports/539ff28796aede3348c013b2"

}

where in the request:

Attribute Type Value
width Integer

Width of the exported image (in pixels).

Set to zero (0) to either use the original width or calculate the width from the specified height and original aspect ratio

For remarks and examples, see Size and aspect ratio.

height Integer

Height of the exported image (in pixels).

Set to zero (0) to either use the original height or calculate the height from the specified width and original aspect ratio

For remarks and examples, see Size and aspect ratio.

publication String

An identifier of the place where the export is used.

This is a free-form string that will be shown in the export management dialog.

preset URL (String) URL of a CMS export preset to be used for supplying additional parameters.

API response

On success, the response is:

1

2

200 OK

Content-Type: application/vnd.fotoware.export-data+json

with response body:

01

02

03

04

05

06

07

08

09

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

{

"export": {

"source": "...",

"json": "...",

"image": {

"normal": "...",

"highCompression": "...",

"doubleResolution": "..."

},

"widget": "...",

"size": {

"w": 921,

"h": 627

}

},

"caption": {

"label": "...",

"tooltip": "..."

},

"publication": {

"text": "..."

},

"metadata":{

"FIELD": "VALUE" | ["VALUE1", "VALUE2", ...],

...

}

}

where:

Attribute Type Value
export.source URL (Asset)

URL of the exported asset.

Can be used to access the details of the asset using the API or to display the details in a browser.

export.json URL (object)

JSON representation of the export.

Identical to this JSON representation

export.image URL (JPEG image) Processed and exported asset (normal version)
export.highCompression URL (JPEG image) Processed and exported asset (smaller file size and potentially reduced quality)
export.doubleResolution URL (JPEG image) Processed and exported asset (doubled resolution, for Retina and similar displays)
export.widget URL (HTML)

An HTML widget containing the processed and exported asset with a tooltip and caption and optional additional behavior, if enabled during export

Can be embedded using an iFrame.

export.size.w Integer Width of the exported image (normal version) in pixels
export.size.h Integer Height of the exported image (normal version) in pixels
caption.label String Caption string, if specified during export
caption.tooltip String Tooltip string, if specified during export
publication.text String Name of publication (free-form string), if specified during export
metadata Dictionary

Metadata of the asset when it was exported.

The keys in this dictionary are the field numbers (as strings).

The values are either strings (for regular fields) or arrays of strings (for bag fields).

Size and aspect ratio

The size of the exported image is specified using the width and height parameters in the request.

If both parameters are set to zero (0), then the asset is exported in its original dimensions.

If exactly one of the parameters is non-zero, then that dimension of the exported image will be exactly as specified, whereas the other dimension (given as zero) will be calculated from it such that the original aspect ratio of the image is maintained. For example, if the image is 4:3, and the width in the request is set to 400, the height will be 300.

Note: It is not allowed to set both dimensions to non-zero values. Doing so will result in a response of 400 Bad Request. This is because specifying both dimensions would require cropping the image, which is currently not supported in the export API. Also, if images need to be cropped, you may typically want the user to select a crop frame. In this case, we recommend using the CMS export widget.

If your original images are all a specific known size (800x600, for example) and you want images to be exported in that same size, set both parameters to zero.

Example

Consider exporting a source asset of size 4000x3000:

Width Height Exported width Exported height
0 0 4000 3000
400 0 400 300
0 600 800 600
400 400 Bad request Bad request

Getting the preset URL

To use a preset with the export API, you must first create an export preset manually and share it.

To get the URL of the preset, you can use the browser's development console while displaying the list of presets in the CMS export dialog or a web debugging tool such as Fiddler. You should see a GET request to a URL /fotoweb/me/presets/export, which should contain an entry for your preset, such as:

1

2

3

4

5

{

"name": "My preset", 

"href": "/fotoweb/me/presets/export/5cc6bb338e2ed62920edd536"

...

}

The value of the href attribute is the preset parameter to be used in the export API.

Notifications when exported assets change

If you've made an integration using the Export API and would like to be notified when an asset changes, you can use asset webhooks to trigger a notification.

transfer api send api

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Requirements for using the Archive Agent API
  • Installing Index Manager
  • Indexing PDF documents
  • Collection queries
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