Connects to your code

Every event, on the record.

Clicks and scans land on the record the moment they happen — in your dashboard for every link, and live into your code for links you create over the API. This is what the wire looks like.

Start freeBrowse the catalog
Dashboard2,861
SSE stream1,204
live · synthetic sample
rii — tail -f events

Illustrative click feed: rows of clicks and QR scans, each showing the time, the event type, the short link, the visitor's country and device, and where it can be read — the dashboard for every link, plus the live SSE stream for links created through the API. The sample is synthetic; the columns are the fields a real click event carries.

5 connections · 4 live · anything else via the REST API or MCP — see the full catalog ↓

The catalog

Everything on the wire, spelled out.

What connects, what flows which direction, and how deep the setup goes — honestly labeled: Live works today, Roadmap carries its date.

Developer

2

AI

1

Communication

1

Automation

1
Yours missing?Request it below — we read every one; meanwhile the REST API and click stream let your own code reach it, for links you create over the API.
Recipes

Three flows you can wire today

No connectors yet — a few lines of your own code on the click stream carry a real-world trigger, through rii.link, into the tool where your team already lives. The stream covers links and QR codes you create over the API.

  • QR scan in Berlin → Slack #growth

    Know the poster works the hour it goes up.

    QR scan — flyer, Berlin
    click event · is_qr: true
    rii.link/berlin-flyer
    your listener → Slack
    #growth · "🔗 Scan — /berlin-flyer, DE"

    today: link + QR via the API (POST /v1/links, /v1/qr) → your SSE listener → Slack incoming webhook

  • Click on /launch → Zapier → sheet

    Log every launch click where the team already looks.

    Click — launch post
    click event
    rii.link/launch
    your listener → catch hook
    Zapier — new row in a sheet

    today: link via the API (POST /v1/links) → your SSE listener → Zapier catch hook

  • QR scan → GA4 event

    Offline scans next to your web analytics, without an app.

    QR scan — packaging
    click event · is_qr: true
    rii.link/unbox
    your relay → GA4
    GA4 — custom event

    today: link + QR via the API (POST /v1/links, /v1/qr) → your SSE listener → GA4 Measurement Protocol

Click stream

Not listed? Stream it or script it.

Every click on your API-created links streams live from GET /v1/events/stream, and the REST API does the rest — your code decides what happens next. Outbound webhooks are on the roadmap for Q1 2027.

Read the API docs
one schema, every click
GET https://api.rii.link/v1/events/stream
event: click
data: { "link_id": "lnk_8h2f0qZ3Tk1mR4vXw9aBcQ",
  "country": "DE", "device": "mobile",
  "is_qr": true, … }
Live, as it happens

Each human click on your API-created links arrives as one server-sent event.

One schema

link_id, country, device, referrer, utm_*, is_qr, rule_matched, timestamp.

API-key auth

The same bearer key as the REST API — create one in Settings → API keys.

Request an integration

Don’t see your tool?

Tell us what you run and what should flow. We read every request and build in order of demand — no promised dates; when it ships, it lands in the catalog above.

01

Your request lands in the same queue our roadmap is built from.

02

Demand decides order — the more teams ask, the sooner it ships.

03

Meanwhile, the click stream and the REST API let your own code reach it today, for links you create over the API.

We only use your email for the ship note — nothing else.

Build on what’s live.

Script links with the REST API, hand them to your agent over MCP, and stream clicks on API-created links as they happen — free to start.

Start freeRead the docs
✓No credit card✓Free forever tier✓GDPR / DSGVO compliant✓Export & leave anytime