QR Code Webhooks with Custom JSON Data

What is a QR code webhook?

A QR code webhook is an HTTP notification triggered when someone opens the URL encoded in a QR code. The QR image itself does not send the notification. A redirect service receives the visit, sends the visitor to a destination, and notifies your application in the background.

With yousnap.me, the same shortlink supports clicks and QR scans. Your custom JSON travels with the webhook, so your application can identify the campaign, printed placement, or product without looking up that context in a separate spreadsheet.

Give each placement its own context

Printed campaigns

Use a different link for a poster, postcard, and event sign. Include a campaign name and placement ID, then compare the response in your own system.

Product packaging

Attach a SKU and batch identifier. Send visitors to a product page while your application receives the context needed to record that interaction.

Event materials

Connect a scan on a booth card or session handout to your workflow. A scan is an interaction signal; it is not proof of identity or attendance.

Set up a scan-triggered webhook

Create a free account, confirm your email if requested, and copy your API key and webhook secret from the dashboard.
Create a link with a destination URL, a JSON data object, and your HTTPS webhook endpoint.
Generate the link’s QR image in PNG or SVG and test it with a phone.
Verify the webhook signature before processing its payload.

curl https://usnp.me/shorten \
  -H "X-API-Key: $USNAP_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "redirect_url": "https://example.com/offer",
    "data": {"campaign": "autumn-demo", "placement": "booth-card"},
    "webhooks": ["https://your-app.example/hooks/scan"]
  }'

Use the returned short_id at https://usnp.me/SHORT_ID/qr?format=svg. The placeholder endpoint above must be replaced with a receiver you control. See the full quickstart for the request and response flow.

How delivery works

Webhook bodies are signed with HMAC-SHA256. Failed deliveries get up to three total attempts. Your receiver should verify the raw request body, handle duplicate deliveries using the hit identifier, and return a successful response promptly. The API reference covers delivery status and signing.

Delivery is subject to plan quotas. Free includes 1,000 webhook deliveries per month; Pro includes 50,000. These allowances are not unlimited delivery guarantees. Keep important business actions behind your own validation: a link can be revisited, shared, or opened by an automated scanner.

Does this replace a QR code designer?

Use yousnap.me when the scan needs to reach your application with data. If you only need a one-off QR image, a simple generator may be enough. If you need a visual campaign suite, compare those requirements separately from the webhook API.

Can a scan tell me who bought something?

No. A scan or click is not a purchase, verified person, or conversion. Correlate the campaign context with a consented signup or purchase event in your own application if you need downstream attribution.

Start with the campaign tracking guide, compare the Bitly webhook options, or review Free and Pro limits.

A QR scan. A page visit. Your next action.