Live
API SHAPESData export
Your links and your click history are yours, and you download them yourself: the whole workspace from the dashboard, or the links you created over the API with an API key. Every export streams as one file.
HOW EXPORT WORKS
→Dashboard: Settings → Export, for workspace owners and admins on every plan. The Links card downloads every link, dashboard- and API-created; the Analytics card downloads the per-click request log for a date range, for all domains or one→On the analytics page, Download CSV exports the clicks behind the current period and domain filter — known bots included, marked in is_bot→Link formats: json is lossless and versioned (format_version) — every redirect option, response body and routing rule; csv is one row per link with the full delivery JSON-encoded in rules_json; nginx and caddy are rule files to re-host the redirects on your own server, one server block per domain→nginx and Caddy can’t express every rule: geo, device, language, time-window and split rules are dropped with a comment naming each one, and that link serves its fallback destination. Keep the JSON export as the complete record→Click log formats: csv or json, one row per request — timestamp, host, path, status, matched rule, bot and QR flags, country, device, browser, OS, referrer, the UTM tags on the short link (utm_*) and on the destination served (dest_utm_*). IP addresses are exported as stored: already truncated to /24 (IPv4) or /48 (IPv6)→Retention: a click export starts no earlier than your plan’s analytics retention — 30 days on Free, 1 year on Premium, unlimited on Enterprise. If you ask for more, the start is moved up and the response says so in X-Export-From, X-Export-To, X-Export-Requested-From, X-Export-Clamped and X-Export-Retention-Days→API: GET /v1/export/links and GET /v1/export/request-logs work with a Read only key. They cover the links created through the API in the key’s environment — the set GET /v1/links lists — and the clicks on them; test keys get an empty click export→Filenames: rii-links-{workspace}-{date}.json, .csv, .nginx.conf or .Caddyfile, and rii-request-logs-{workspace}-{date}.json or .csv — {workspace} is your workspace name as a slug, {date} the UTC day of the export
Export in the reference→ API · Export
Both endpoints, with runnable cURL, the formats and the retention headers.