--- title: "Data Extraction in Unqork" slug: "data-extraction-in-unqork" updated: 2025-09-25T18:50:06Z published: 2025-09-25T18:50:06Z canonical: "docs.unqork.io/data-extraction-in-unqork" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.unqork.io/llms.txt > Use this file to discover all available pages before exploring further. # Data Extraction in Unqork This article provides a comprehensive guideline for **extracting the various types of data** that Unqork stores. Clients can find instructions for extracting meaningful data for their organization. By adhering to these instructions, clients can extract their submission data, attachment data, and other data stored in Unqork. > [!WARNING] > You must generate an access token before using any of these APIs. Please refer to our API documentation for generating an access token for authentication: [https://developers.unqork.io/#section/Authentication](https://developers.unqork.io/#section/Authentication). > This article focuses on the types of data you can extract data from Unqork. To learn how to extract this data and use preconfigured modules to do so, view our [How to: Extract Data From Unqork](/v1/docs/how-to-extract-data-from-unqork) article. Submission DataAttachment DataConfiguration DataStyle Sheets ## Submission Data Extraction And Exporting [Submission data](/v1/docs/submission-data) refers to information stored when end-users interact with your modules and save their inputs. Your end-user creates a new submission (and submission ID) every time they save or submit their data. Clients typically need to access their submission data depending on the context of the data involved. Below are some examples of why extracting submission data might be useful. ### Record Keeping and Compliance - **Audit Purposes**: Clients might need their submission data for auditing or compliance purposes to ensure adherence to industry regulations, internal policies, or legal requirements. ### Data Ownership and Reporting - **Ownership**: Clients might want a copy of all submission data submitted and stored in their [applications](/v1/docs/introduction-to-unqork-applications). - **Analysis and Reporting**: Clients might want information for internal analysis and reporting on business conducted in their Unqork applications. ### Data Migration - **Migration**: Clients might need submission data for a different platform or service. Clients might be interested in preserving this information for future business purposes. ## Extracting Submission Data In this section, you'll explore the ways you can extract your data from Unqork. ### Schema Module Submissions Use the following API format to retrieve the first **50** submissions from your schema module: `https://{host}/api/1.0/modules/{moduleId}/submissions`. You’ll replace `{host}` with your Unqork environment URL and `{moduleId}` with the module ID of your schema module. For example, `https://trainingx.unqork.io/api/1.0/modules/63a4c85986e5d0ecb416c8a7/submissions`. > [!WARNING] > **Check the Response Header**: More items must be retrieved if the **next** link header is present. You’ll find your current API call link and the **next** link that contains the next 50 submissions. > > For example, `https://{host}/api/1.0/modules/{moduleId}/submissions?offset=50)`. > > Repeat the API GET calls until no more new submissions remain, signified by no **next** link being present. ### Schema Workflow Submissions Use the following API format to retrieve the first **50** submissions from your schema workflow: `https://{host}/api/1.0/workflows/{workflowId}/submissions`. You’ll replace `{host}` with your Unqork environment URL and `{workflowId}` with the workflow ID of your schema workflow. For example, `https://trainingx.unqork.io/api/1.0/workflows/63740406be1640f9a87a6b6e/submissions`. > [!WARNING] > **Check the Response Header**: More items must be retrieved if the **next** link header is present. You’ll find your current API call link and the **next** link that contains the next 50 submissions. > > For example, `https://{host}/api/1.0/workflows/{workflowId}/submissions?offset=50)`. > > Repeat the API GET calls until no more new submissions remain, signified by no **next** link being present. --- ### FAQ #### Do I use my Unqork Express or Designer environment URL in the {host} portion of the API? This API can be used with either the Unqork Express or Designer environment URL. #### Is it possible to use the API to get more than 50 submissions at one time? The maximum number of submissions that can be retrieved with a single API call is 50. However, you can use scripting to automate the process and run additional API calls. #### Are there any alternate methods that can be used to export submissions? If the Bulk Record Data Export feature is available in your environment, use it to export submissions from each Record Collection. ## Exporting Submission Data Unqork's internal API supports exporting submission data to the cloud or locally using `https://{environment}.unqork.io/fbu/uapi/bulk-operations/export`. > Discover how to export submission data in our [Bulk Data Operations: Export](/v1/docs/bulk-data-operations-export) article. ### Resources - [Get Module Submissions](https://developers.unqork.io/#operation/getModuleSubmissions) - [Get Workflow Submissions](https://developers.unqork.io/#operation/getWorkflowSubmissions) - [Paging](https://developers.unqork.io/#section/Paging) ## Extracting Attachment Data Attachment data refers to any images or files saved as part of a submission. Based on the configuration and the files stored, these might include CSV/Excel, PDF, or image files. ### Schema Module Submissions Use the following API format to retrieve the first **50** submissions from your schema module: `https://{host}/api/1.0/modules/{moduleId}/submissions`. You’ll replace `{host}` with your Unqork environment URL and `{moduleId}` with the module ID of your schema module. In the response and inside the submissions associated with attachment data, links to that attachment data display in the format of a **Cloud Storage Delivery** link: `https://{host}/fbu/files/{filePath}?signature={signature}`. > [!WARNING] > **Check the Response Header**: More items must be retrieved if the **next** link header is present. You’ll find your current API call link and the **next** link that contains the next 50 submissions. > > For example, `https://{host}/api/1.0/workflows/{workflowId}/submissions?offset=50)`. > > Repeat the API GET calls and retrieve the attachment data from the **Cloud Storage Delivery** links until no more new submissions remain, signified by no **next** link being present. ### Schema Workflow Submissions Use the following API format to retrieve the first **50** submissions from your schema workflow: `https://{host}/api/1.0/workflows/{workflowId}/submissions`. You’ll replace `{host}` with your Unqork environment URL and `{workflowId}` with the workflow ID of your schema workflow. In the response and inside the submissions associated with attachment data, links to that attachment data display in the format of a **Cloud Storage Delivery** link: `https://{host}/fbu/files/{filePath}?signature={signature}`. > [!WARNING] > **Check the Response Header**: More items must be retrieved if the **next** link header is present. You’ll find your current API call link and the **next** link that contains the next 50 submissions. > > For example, `https://{host}/api/1.0/workflows/{workflowId}/submissions?offset=50)`. > > Repeat the API GET calls and retrieve the attachment data from the **Cloud Storage Delivery** links until no more new submissions remain, signified by no **next** link being present. --- ### FAQ #### How long is the Cloud Storage Delivery link valid? 24 hours. #### Will the Cloud Storage Delivery link change when running the same Get Submissions API call more than once? Yes. Each time you make the API call, you’ll receive a new Cloud Storage Delivery link. The previous link(s) are still valid 24 hours from the time the link was generated after the previous API call(s). ### Resources - [Get Module Submissions](https://developers.unqork.io/#operation/getModuleSubmissions) - [Get Workflow Submissions](https://developers.unqork.io/#operation/getWorkflowSubmissions) - [Paging](https://developers.unqork.io/#section/Paging) - [Cloud Storage Delivery](https://developers.unqork.io/#section/Cloud-Storage-Delivery) ## Extracting Configuration Data Exporting configuration data lets the client control ownership of their intellectual property. Copying the module or workflow definitions lets you duplicate your configuration in another module or workflow in the same or different environment. Storing the module or workflow definitions lets you recreate the module or workflow at any time. ### Module Definition 1. Log in to your environment. 2. Navigate to your workspace. 3. Navigate to a [module-type](/v1/docs/working-with-module-type-apps) application containing your module. 4. Open the module in the Module Builder. 5. At the top right of the Module Builder, click ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(33).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A55Z&se=2026-11-07T18%3A57%3A55Z&sr=c&sp=r&sig=S9XKZiLm2dL29lNV%2BW%2BlqYY%2B%2BizCzrBXNoiJ6eRmbIM%3D) **(ellipsis)** and select **Copy** **Module** **Definition**. The module definition saves to your computer’s clipboard. 6. The module definition has now been successfully copied to the clipboard and is ready to be pasted into a text or code editor. > [!WARNING] > If you encounter any difficulties, please contact Unqork Support at [support.unqork.com](http://support.unqork.com/). ### Workflow Definition 1. Log in to your environment. 2. Navigate to your workspace. 3. Navigate to a [workflow-type](/v1/docs/working-with-workflow-type-apps) application containing your workflow. 4. Open the workflow in the Workflow Builder. 5. At the top right of the Module Builder, click the ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(33).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A55Z&se=2026-11-07T18%3A57%3A55Z&sr=c&sp=r&sig=S9XKZiLm2dL29lNV%2BW%2BlqYY%2B%2BizCzrBXNoiJ6eRmbIM%3D) **(ellipsis)** and select **Copy Workflow Definition**. The workflow definition saves to your computer’s clipboard. 6. The workflow definition has now been successfully copied to the clipboard and is ready to be pasted into a text or code editor. > [!WARNING] > If you encounter any difficulties, please contact Unqork Support at [support.unqork.com](http://support.unqork.com/). --- ### FAQ #### What should I consider when using an existing module or workflow definition? When pasting the module or workflow definition, you must consider any specific configurations that existed in the original environment or application. Sometimes, these specific configurations might not exist in the new environment or application. For example, [Plug-In](/v1/docs/plug-in-component) component services, references to other module IDs, module RBACpermissions, and so on. ## Extracting Style Sheets Unqork's Style Team can style an environment with Custom CSS. CSS is a stylesheet language used to customize the look and feel of a website's content. You can upload a style sheet to [Style Administration](/v1/docs/style-administration) in the environment settings. 1. Login into your environment. 2. At the top right of the page, click **Settings ▾** and select **Administration**. 3. Under Environment, click **Style Administration**. 4. In the **Styles Admin** table, locate the style you want to export. 5. At the top right, click **Manage ▾** and select **Download**. 6. Check the downloads in your browser to view the downloaded file. --- ### FAQ #### Can I delete the style after downloading it? Yes. To learn more, view our [Style Administration](/v1/docs/style-administration) article in the Documentation Hub. ### Resources - [Style Administration](/v1/docs/style-administration) End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product. APIs (application programming interfaces) are a set of protocols and definitions developers use to build and integrate application software. APIs act as the connective tissue between products and services. A place on your operating system that stores recently copied content. The clipboard only stores one item at a time. RBAC (Role-Based Access Control) is a method to control system access for authorized users. The role in RBAC refers to the levels of access employees have to a network. Cascading Style Sheets (CSS) is a style sheet language used for presenting how a HTML or XML document looks to end-users.