Overview
The manifest describes how your LinkApp appears in the Linktree marketplace. Keep the copy clear, benefit-led, and easy for users to scan.Minimal Manifest Example
linkapp.config.ts
Field Reference
| Field | Type | Required | Quick guidance |
|---|---|---|---|
name | string (3-50 chars) | ✓ | Human-readable app name in title case (kebab-cased to generate LinkApp ID) |
tagline | string (3-200 chars) | ✓ | Short benefit statement for marketplace cards |
description | string[] | ✓ | One or more paragraphs explaining value, features, and audience |
manifest_version | string (semver) | ✓ | Currently always "1.0.0" |
version | string (semver) | ✓ | Your app release version (follow semantic versioning) |
category | grow | sell | share | other | ✓ | Choose the primary outcome your app delivers |
search_terms | string[] (1-10) | ✓ | Keywords users might search (avoid duplicates) |
supporting_links | object | ✓ | Provide ToS & privacy URLs; docs/site optional |
author | object | ✓ | List who built the app and how to reach you |
Supporting Links
All URLs must be publicly accessible HTTPS links.Author Details
Use real contact information so testers and customers can reach you. Only accounts listed below can access the app while it is in draft.LinkApp ID Generation
Important: The LinkApp ID is automatically derived from thename field by converting it to kebab-case:
"Weather LinkApp"→weather-linkapp"Maps"→maps"Bands In Town"→bands-in-town
Versioning & Validation
- Bump
versionfor every release using semantic versioning (major.minor.patch). - Run
linkapp buildto validate the manifest locally before deploying. - Fix common errors such as missing required fields, non-semver versions, or invalid URLs/emails.