API for analysis output files functional

The resources provided by the API are protected. You can submit the credentials by a) HTTP basic access authentication or b) an API key.

Keep in mind that the tokens and/or API-Keys will be visible to the public. That is okay for workflows which generate public resources.

If your workflow produces sensitive resources consider consuming the artifacts by an own backend system in order to hide this token from the public.

Preparation

1. Find the OUTPUT Button at your Workflow Instance Screen on MoveApps
2. In the Workflow Instance Output Screen localize and press the button API ACCESS
3. Press REGISTER
4. Note values of Username and Password (aka Token)
5. Localize and press the link on this screen named this overview
6. On this overview all the files produced by your Workflow Instance are listed. Use these links to your seletion of files for the next sections.

The mentioned overview for this example (use something that can parse XML!).

Just a basic list of links

• some PDF document (opens in new tab)
• some ZIP file (will be downloaded)
• some CSV file (will be downloaded)

Embed content via HTML tags

• You have to use the access method API Key (Browsers do not allow links with embedded credentials)
• Pro: easy - no code
• Con: no metadata (as if the file was modifiedAt) accessible
• Con: not that dynamic - you cannot react to changes done in the workflow (like dynamic file names)

Integrate content via JavaScript

• Pro: consumes and uses metadata (like modifiedAt)
• Pro: reacts to changes in the workflow
• Con: Scripting must be enabled

See here a generated Morning Report PDF

See here tracks of our favorite Max Planck species: White storks that were born in Radolfzell.