API referenceEndpoints

QR codes and app links

Create a branded code, route each device, and connect the visit to reported events.

Create and export

Use Links → QR codes and NFC in the dashboard, or call the partner API from your server. Every code belongs to a campaign and keeps the same HTTPS tracking URL when you edit its destinations. Owners and admins can edit; account members can view and export.

MethodPathPurpose
POST/v1/smart-linksCreate with campaignId, settings and a stable requestId UUID. Reuse the UUID on retries.
GET/v1/smart-links?page=0List 50 placements at a time.
GET / PUT/v1/links/:id/smartRead or replace settings. enabled:false pauses new arrivals.
GET/v1/links/:id/qr.svgDownload the print-ready SVG.
GET/v1/links/:id/qr.pngDownload a 1024 px PNG.
GET/v1/links/:id/smart/stats?days=30Read visits and reported events; days accepts 1–365.
Create a code
curl 'https://track.acrune.com/v1/smart-links' \
  -H 'Authorization: Bearer YOUR_SERVER_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"campaignId":"YOUR_CAMPAIGN_UUID","requestId":"YOUR_REQUEST_UUID","settings":{"name":"Homepage download","webUrl":"https://yourbrand.example/download","iosUrl":"https://apps.apple.com/app/idYOUR_APP","androidUrl":"https://play.google.com/store/apps/details?id=YOUR_PACKAGE","style":"dots","color":"#202020","mark":"A","nativePath":"/welcome","campaign":"homepage"}}'

Keys stay on your server. Styles are square, rounded or dots. A centered monogram or PNG/JPEG/WebP logo is checked by decoding the final image at two sizes before saving. The quiet zone remains white; always test the final print with real phones.

Installed apps and store fallback

The web route detects the device and chooses iosUrl, androidUrl or webUrl. Direct native opening also requires your app's Universal Links/App Links configuration on a dedicated branded domain. The studio shows whether that configuration exists; it does not claim the app has been tested.

CallBody / response
POST /v1/links/:id/openYour app's backend sends eventId (stable UUID), os (ios/android), and source (qr/link/app). Acrune returns clickId and nativePath. Keep the click ID for later events; retrying the same open never creates a second click.

Never ship your API key in the app. Android can read acr_cid from Google Play Install Referrer. iOS needs a separate identity or claim flow to reconnect anonymous pre-install traffic; this product does not invent a fingerprint match. If a web handoff already supplied a click ID, keep it instead of reporting a second open.

Report the outcome

POST /v1/smart-events with a server key holding write scope. Supported kinds are install, signup, trial, purchase, renewal and refund. Every event needs eventId, clickId and the original occurredAt timestamp. Monetary events additionally require integer amountMinor and an ISO currency; other kinds omit both.

Purchase event
{
  "eventId": "order_123:paid",
  "clickId": "THE_ATTRIBUTED_CLICK_ID",
  "kind": "purchase",
  "occurredAt": "2026-09-17T12:00:00.000Z",
  "amountMinor": 4900,
  "currency": "GBP"
}

Identical retries return the original event. Reusing an eventId with changed data returns 409. Attribution cannot cross tenants. Test-key events remain separate from live events. Visit windows use visit time and event windows use occurredAt, so the report is not a cohort conversion rate.

These are authenticated server-reported analytics, not independently verified payments or settled balances. Verify provider webhooks in your backend before forwarding them. These endpoints do not create payout ledger entries. QR source tags are reported context, not proof of a camera scan or a unique person.