Skip to content

Routes & Deep Links

A route is a URL path that maps to content inside your mobile app. When someone taps a Tolinku link, the route determines where they go: which screen in your app, which fallback URL if they don’t have the app, and what the link preview looks like on social media.

Routes list in the Tolinku dashboard showing static and dynamic routes with their prefixes, types, and status

Every Appspace comes with a default /install route out of the box. You do not need to create it. This route detects the visitor’s device and sends them to the right store:

  • iPhone/iPad: Redirects to your iOS App Store URL
  • Android: Redirects to your Google Play Store URL
  • Desktop/other: Redirects to your web fallback URL, or shows a branded download page

The install route uses the store URLs from your App Config. Once those are saved, https://your-app.tolinku.com/install works immediately. This is the fastest way to get a “download our app” link live.

Tolinku supports two route types you can create: static and dynamic.

A static route has a fixed path like /download or /promo. Every user who taps the link goes to the same destination. Use these for marketing campaigns, landing pages, and general-purpose links where everyone gets the same experience.

A dynamic route includes a path parameter (:token) like /product/:token. The token is replaced with a value when you share the link (e.g. /product/abc123), making each link unique.

Dynamic routes come in two flavors:

  • Basic dynamic routes: The token is passed to your app for routing. Your app parses it and navigates to the right screen. The landing page (if any) uses your default branding.
  • API-enriched dynamic routes: You connect an API endpoint that Tolinku calls with the token. Your API returns data (product name, user avatar, custom message) and the landing page displays that data. This creates a personalized experience for each link.
StaticDynamicDynamic + API
Path/promo/invite/:token/product/:token
Use caseCampaigns, landing pagesGroup invites, magic loginMerchant payments, personalized content
Landing pageSame for everyoneDefault brandingPersonalized per token
Server workNoneNoneYour API serves data

For a deep dive, see Dynamic Routes.

When a user taps a Tolinku link:

  1. Mobile with app installed: The link opens directly in your app via Universal Links (iOS) or App Links (Android). Your app receives the full URL and navigates to the matching screen.

  2. Mobile without app: The user sees a landing page (if configured) or is redirected to the App Store / Play Store / your fallback URL.

  3. Desktop: The user is redirected to your web fallback URL, or sees a landing page with a prompt to download the app.

Each route has several optional settings:

  • Landing page template: Choose between a generic branded page, a custom-designed page (built with the visual editor), or no landing page (direct redirect).
  • Web fallback URL: Where desktop and non-app users go. Overrides the Appspace default.
  • Universal Links / App Links: Toggle whether the route is included in your AASA and assetlinks.json files for direct app opening.
  • OG tags: Custom title, description, and image for social media previews.
  • Expiration: Set a date or click limit after which the route stops working.
  • API endpoint: For dynamic routes, an endpoint that returns data for the landing page.
  • Short link: Every route automatically gets a 7-character short code. For static routes, the short link works as a complete URL (e.g. links.yourapp.com/x4km9q2). For dynamic routes, append the token (e.g. links.yourapp.com/x4km9q2/abc123). You can regenerate the short code from the route edit page.
PlanRoutes
Free5
StandardUnlimited
GrowthUnlimited
ScaleUnlimited