Forge your
first link.

Start with three things: a configured domain, an app record, and an API key scoped to the target environment.

Create links through the admin API. Every link belongs to one tenant and environment, making campaign routing and analytics isolation explicit.

curl -X POST https://your-domain.com/api/v1/admin/links \
  -H "Authorization: Bearer $LINKFORGE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "slug": "summer",
    "iosUrl": "myapp://offers/summer",
    "androidUrl": "myapp://offers/summer",
    "webUrl": "https://example.com/summer"
  }'

Resolve from a trusted backend or SDK client. Platform, install state, and policy select the best destination while preserving attribution context.

const response = await fetch(
  "https://your-domain.com/api/v1/sdk/short-link/resolve",
  {
    method: "POST",
    headers: {
      "x-api-key": process.env.LINKFORGE_API_KEY,
      "content-type": "application/json",
    },
    body: JSON.stringify({ slug: "summer", platform: "ios" }),
  },
);

const { destinationUrl } = await response.json();

• API keys stay scoped to one environment.
• Unknown links return a stable 404 contract.
• Analytics events can be recorded after resolution.

Point your hostname to LinkForge, then configure the iOS Team ID, bundle ID, Android package name, and signing fingerprints. LinkForge generates both association files.