MIT licensed · read the source

Links are an API call,
not a form field.

A typed REST API, real-time webhooks and scoped API keys — the same surfaces the dashboard is built on. Automate link creation, wire up attribution, and read every line of the source that does it.

⌘

REST API

A typed, versioned HTTP API. Create a link, read its analytics, manage domains — the dashboard talks to the same endpoints you do.

⇉

Real-time webhooks

Subscribe to events like conversion.recorded and get them pushed to your endpoint the moment they happen.

⚿

Scoped API keys

Per-workspace keys you can rotate and revoke, so conversions attribute back to the key that reported them.

Create a link

One request, one link.

Authenticate with a workspace API key and POST a destination. You get back the full link — the same object the dashboard shows — so you can print its QR or edit where it points later without changing the printed code.

Bearer API keyReturns a Link
POST /links
curl -X POST "$SNAPURL_API_URL/links" \
  -H "Authorization: Bearer $SNAPURL_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "destination": "https://acme.com/spring-2026",
    "slug": "spring-sale"
  }'

# → 201 Created — returns the Link, including its slug and short URL
React to what happens next
Webhook delivery
POST https://your-app.example.com/webhooks/snapurl

{
  "event": "conversion.recorded",
  "data": {
    "linkId": "...",
    "value": { "amount": 4900, "currency": "USD" }
  }
}

Attribution, server-side.

Your own site reports a conversion with POST /conversions, scoped to the API key that owns it. SnapURL pushes a conversion.recorded webhook onward, so your analytics attribute the click without a third-party pixel on anyone's device.

It keeps working for the growing share of visitors whose browsers block pixels outright.

Open source, all the way down

The API, the redirect service and this dashboard are MIT licensed. Read exactly how a click is recorded, fork it, or run the whole thing yourself. There is no closed core waiting to bill you.

Build with it today.

Create a workspace, mint an API key and start shipping links from code — or clone the repo and run it yourself.