<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>🌐 2. Using the Dataspace API</title>
    <link>/02-dataspace-api.html</link>
    <description>This section provides examples on how to perform key dataspace operations within your environment using the API. Designed for developers, learn to test and validate dataspace functionality using pre-built Postman collections, and create custom data transfer test workflows.&#xA;Table of Contents Name Purpose 2.1 Launching the Postman GUI Set up Postman GUI and import pre-built test collections 2.2 Pre-configuration Test Sequence Configure your dataspace using automated preconfiguration tests 2.3 Dataspace Test Sequence Execute comprehensive dataspace validation tests 2.4 Setup/Run a Data Transfer Create custom workflows to exchange data between connectors</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="/02-dataspace-api/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>2.1 Launching the Postman GUI</title>
      <link>/02-dataspace-api/01-use-postman-gui.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/02-dataspace-api/01-use-postman-gui.html</guid>
      <description>The following section explains how to launch the Postman GUI application in your dataspace environment. This is essential for running the built-in test sequences, as well as writing your own data exchange workflows. The Postman GUI is a prerequisite to further sections throughout this documentation.&#xA;Prerequisites: You need to be connected via DCV in order to use the Postman GUI. Postman GUI requires an account to run tests. If you do not have an account, please register at the official Postman website Log in to your account Connect to your dataspace via DCV</description>
    </item>
    <item>
      <title>2.2 Pre-configuration Test Sequence</title>
      <link>/02-dataspace-api/02-preconfigure.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/02-dataspace-api/02-preconfigure.html</guid>
      <description>The default dataspace testbed environment comes with several Postman scripts that can be used to test the basic functions of the testbed service. This section outlines how to execute the preconfiguration Postman test sequence via the various access methods.&#xA;Command to run the Postman test To run the preconfiguration Postman script, you need to run the following command from the testbed directory.&#xA;postman-cli collection run TestbedPreconfiguration.postman_collection.json You can do this from an SSH session, via the code-server IDE, or via a DCV connection. The procedure for each method is outlined below:</description>
    </item>
    <item>
      <title>2.3 Dataspace Test Sequence</title>
      <link>/02-dataspace-api/03-test.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/02-dataspace-api/03-test.html</guid>
      <description>How to run the Postman Testsuite Script Prerequisites: Please complete the Pre-Config Test Sequence before proceeding to this section.&#xA;Running from the CLI (IDE, SSH or DCV Terminal) You should still be connected to your dataspace following completion of the Pre-configuration Test Sequence&#xA;To test different components, you will need to run the corresponding test command for the component you wish to test</description>
    </item>
    <item>
      <title>2.4 Setup/Run a Data Transfer</title>
      <link>/02-dataspace-api/04-transfer.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/02-dataspace-api/04-transfer.html</guid>
      <description>Prerequisites: This tutorial uses Postman GUI. Please follow the steps in Setup Postman GUI first.&#xA;Prepare your data After importing the original Testsuite files, you will need to modify some requests to transfer your data between the sample connectors A and B.&#xA;Expand the Testsuite / Connector / Set-up folder in left panel:</description>
    </item>
  </channel>
</rss>