---
title: "Unqork Express URL Patterns"
slug: "unqork-url-patterns"
description: "Learn about Unqork's URL patterns for applications, modules, and workflows to effectively navigate and redirect within your application context."
updated: 2025-11-12T16:03:18Z
published: 2025-11-12T16:03:18Z
canonical: "docs.unqork.io/unqork-url-patterns"
---

> ## 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.

# Unqork Express URL Patterns

Many **Express** **URL** **patterns** are useful for a Creator in Unqork. For example, understanding URLs/URL structure can help you to use them in your application to redirect an end-user to a specific page after performing an action. The pattern of these URLs depends on the application, module, or workflow context. In this reference guide, you’ll learn about the different URL patterns native to Unqork to better view and explore your application elements.

## Application Context

All Unqork URLs begin with `https://{your-environment}.unqork.io`. Your environment name specifies the environment where the application, module, or workflow exists. For applications, the URL is further specified using `app`, followed by the application path. From here, the URL will differ depending on whether the application is a module or workflow- type application. Using an application URL pattern lets you preview a module in the application context. This includes the [Header](/v1/docs/header-module) and [Footer modules](/v1/docs/footer-module) in Express View.

> When directing to Express URLs in Staging or UAT environments, like the [Training environment](https://training.unqork.io/), an `x` is added after the environment name. This extra character does not display in Pre-Production or In-Production environments, or when using a Vanity URL.

- **Module With Application Context**: `https://{your-environment}.unqork.io/app/{appPath}#/display/{moduleId}`
  - Example: `https://trainingx.unqork.io/app/my-application#/display/ads90g7gh7867d908ad3gjop`
- **Workflow With Application Context**: `https://{your-environment}.unqork.io/app/{appPath}#/workflow/{workflowPath}`
  - Example: `https://trainingx.unqork.io/app/my-workflow-application#/display/my-workflow`

## Module Context

The URL pattern of individual modules requires specifying the environment where the module is located. This URL is followed by `display`, and the `moduleId` or `modulePath` of that module. To direct to a specific submission stored in that module, add the specific `submissionId`, followed by the `moduleId` again.

- **Module**: `https://{your-environment}.unqork.io/#/display/{moduleId}`
  - Example: `https://trainingx.unqork.io/#/display/ads90g7gh7867d908a`
- **Module With Submission**: `https://{your-environment}.unqork.io/#/display/{moduleId}/{submissionId}/{moduleId}`
  - Example: `https://trainingx.unqork.io/#/display/ads90g7gh7867d908ad3gjop/d90s7g09sdj0g98sdk20tsav/ads90g7gh7867d908ad3gjop`

## Workflow Context

The workflow URL pattern follows a similar formula to module and applications, but lets you direct to a specific step in the workflow. After specifying the environment where the workflow exists, the URL includes `workflow` , followed by the workflow path. This URL pattern can be built on to specify a particular navigation step in the workflow or to a specific submission stored in that workflow.

- **Workflow**: `https://{your-environment}.unqork.io/#/workflow/{workflowPath}`
  - Example: `https://trainingx.unqork.io/#/workflow/my-workflow`
- **Workflow With Navigation Step**: `https://{your-environment}.unqork.io/#/workflow/{workflowPath}/{stepPath}`
  - Example: `https://trainingx.unqork.io/#/workflow/my-workflow/task-3`
- **Workflow With Submission**: `{your-environment}.unqork.io/#/workflow/{workflowPath}/submission/{submissionId}`
  - Example: `https://trainingx.unqork.io/#/workflow/my-workflow/submission/d90s7g09sdj0g98sdk20tsav`

A URL (uniform resource locator) is a unique identifier used to locate a resource on the internet. Also known as a web address.

Also known as Unqork Users, or Designer Users; is anyone who is inside the Unqork platform.

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.

Express View is how your end-user views your application. Express View also lets you preview your applications to test your configuration and view the styling. This is also the view your end-users will see when interacting with your application. After configuring a module, click Preview in the Module Builder to interact with the module in Express View.