Skip to content
Tolinku Docs

Creating Routes

Creating a route

Section titled “Creating a route”

  1. Go to Routes in the sidebar and click Create Route.

  2. Choose the link type: Dynamic (with a :token parameter) or Static (fixed path).

  3. Enter a prefix. This is the URL path for your route. For example, if you enter invite, your links will look like https://your-domain.tolinku.com/invite (static) or https://your-domain.tolinku.com/invite/abc123 (dynamic).

  4. Give it a name. This is an internal label shown in the dashboard and analytics. It is not visible to users.

  5. Configure the remaining settings (landing page, fallback URL, OG tags) and click Save.

Prefix rules

Section titled “Prefix rules”

The prefix is the most important part of your route. It defines the URL path and cannot be changed after creation without creating a new route.

  • Length: 3 to 63 characters
  • Characters: Lowercase letters, numbers, and hyphens only
  • Restrictions: Cannot start or end with a hyphen
  • Uniqueness: Must be unique within your Appspace

Landing page behavior

Section titled “Landing page behavior”

Each route can use one of three landing page modes:

  • Generic: A branded landing page with your app name, logo, and download buttons. Works well for most links.
  • Custom: A page you design using the visual builder. Choose from templates or build from scratch.
  • None: No landing page. The user is immediately redirected to the app, store, or fallback URL.

For dynamic routes, the default is Generic. For static routes, the default is None (direct redirect).

Fallback URL

Section titled “Fallback URL”

The web fallback URL determines where users go when they cannot open your app (desktop browsers, users without the app). If you leave this empty, the route falls back to the Appspace-level fallback URL set in App Config.

A typical setup:

ScenarioDestination
Mobile, app installedOpens directly in the app
Mobile, no appApp Store or Play Store
DesktopYour fallback URL (e.g. marketing site)
Section titled “Universal Links and App Links”

By default, every route is included in your Apple App Site Association (AASA) and Digital Asset Links files. This means iOS and Android will open your app directly when a user taps the link, without showing a browser first.

You can disable this per route if you want certain paths to always open in the browser. Toggle the Universal Links / App Links setting on the route form.

Configuration checklist

Section titled “Configuration checklist”

The route form shows a checklist to help you track what has been configured:

  • Prefix and name (required)
  • Fallback URL
  • Universal Links enabled
  • OG tags
  • API endpoint (dynamic routes)

You do not need to complete everything before saving. Only the prefix and name are required.