Redirect a legacy (PartnerStack) link
Backwards-compatible redirect for links created in a previous affiliate tool (e.g. PartnerStack) that were migrated into Introw. During a migration every old link is mapped to its newly generated Introw affiliate link. Point your old links at this endpoint with a redirect rule on your side; Introw resolves the mapping and 302-redirects to the matching Introw link (/r/{code}), which then records the click, sets the first-party _introw_aff attribution cookie, and forwards the visitor to the campaign destination.
No key required. The lookup is keyed by the globally-unique original URL, so no API key or publishable key is needed.
How the original URL is captured, in priority order:
- The
uquery parameter (recommended): your redirect rule forwards the original absolute URL, e.g.https://api.introw.io/api/v1/affiliate/legacy-redirect?u=https%3A%2F%2Fgo.acme.com%2Fabc. - The
X-Original-URLorX-Forwarded-Urirequest header (reverse-proxy / CNAME setups). - The
Refererheader (fallback).
The captured URL is normalized before lookup (scheme and host lowercased, default ports and a trailing slash stripped, query params sorted; path and query values stay case-sensitive), so the value you forward does not need to match byte-for-byte.
Query Parameters
The original (old) link to resolve, as an absolute URL. URL-encode the value. If omitted, Introw falls back to the X-Original-URL / X-Forwarded-Uri headers, then Referer.
Response
A match was found. Redirects to the mapped Introw affiliate link (/r/{code}), which in turn records the click and forwards to the campaign destination.