Developer integration

7stamp Webhooks

Available

Push every loyalty event from 7stamp to your own systems in real time. No polling and no scheduled API calls. Events arrive as HTTPS POST requests within seconds of happening.

Use webhooks to keep your CRM, ERP, or custom backend in sync with what is happening on the loyalty side: who joined, who got a stamp, who redeemed a voucher, who triggered a birthday gift, and who became inactive. Then your systems decide what to do with that data.

Open API reference Open 7stamp Admin

What you can do with webhooks

Webhooks are the outbound side of the integration stack. They mirror customer and reward activity into the systems you already trust for sales, service, analytics, and messaging.

Mirror loyalty history into your CRM

Every stamp, voucher, birthday, and inactivity trigger lands on the customer record in your CRM. You see the full loyalty timeline next to sales, calls, and tickets without logging into 7stamp.

Trigger your own messaging stack

When a customer redeems a voucher, send a thank-you SMS from your existing SMS gateway. When a customer hits the goal, post a celebration in Slack. When someone becomes inactive, route the case to your account manager.

Power analytics and reconciliation

Stream events into your BI tool, warehouse, or reconciliation pipeline. Match voucher redemptions against POS receipts and calculate loyalty ROI in your own metrics.

Card event types

SCAN — A card received a scan/stamp action.

REWARD_EARNED — A reward was earned on the card.

VOUCHER_ISSUED — A voucher was issued.

VOUCHER_REDEEMED — A voucher was redeemed.

LOTTERY_WIN — A lottery resulted in a win.

DELIVERY_INSERT — A delivery-insert flow was recorded.

CARD_JOINED — A customer joined a card.

CARD_CAMPAIGN — A card campaign event occurred.

BIRTHDAY_GREETING — A birthday greeting event occurred.

ADMIN_VOUCHER_ISSUE — An administrator issued a voucher.

CARD_ADDED_TO_WALLET — A customer added the card to their wallet.

CARD_REMOVED_FROM_WALLET — A customer removed the card from their wallet.

Build a safe webhook receiver

Acknowledge after durable handling

Your endpoint should accept HTTPS POST, validate the request shape, persist or queue the event, then return a successful 2xx response. Do not make a slow CRM or messaging call before the acknowledgement if it can be queued safely.

Correlate with External ID

Every related event can carry the External ID and optional External Source that you used when creating or scanning the card. Use this pair to update your own CRM, POS, or order record without guessing from a name or email.

Make delivery idempotent

Store a durable processing key or event fingerprint before triggering side effects. If your receiver sees the same delivery again, it should not add a duplicate CRM note, voucher, or message. Treat the endpoint URL as a secret.

Example event payload shape

Copy this into your automation step json

{
  "event_type": "SCAN",
  "scanned_at": "2026-07-23T12:34:56Z",
  "user_card_id": 123,
  "card_template_id": 42,
  "card_template_name": "Coffee Loyalty",
  "stamps_added": 1,
  "stamps_before": 4,
  "stamps_after": 5,
  "amount": 24.5,
  "external_order_id": "order_2048",
  "external_id": "crm_contact_8821",
  "external_source": "hubspot"
}

Configure and test a webhook

Create an HTTPS endpoint in your backend, CRM integration layer, Make webhook, or Zapier Catch Hook. Make sure you control the destination before copying its URL.

In 7stamp Admin, open Stamp Cards → API & Integrations → Webhooks.

Add the endpoint URL and select only the event types the receiving workflow actually needs.

Save the profile settings, then trigger a disposable test scan or card action to produce an event.

Inspect the received payload. Match External ID and External Source to the expected record and confirm the receiver returns a successful response.

Enable CRM, voucher, or messaging side effects only after you have replay-safe handling and monitoring for failures.

No-code options: Make and Zapier

In Make, use Webhooks → Custom webhook to generate a receiving URL and paste it into the 7stamp profile. In Zapier, use Webhooks by Zapier → Catch Hook for the same purpose. The 7stamp profile owns the subscription because the current API does not expose automatic webhook registration endpoints.

Security and delivery contract

Use the Webhooks section of the public OpenAPI reference as the source for the current payload schema and field meaning. Require HTTPS, keep the receiver URL out of public logs, and make processing idempotent. Confirm the request-authentication/signature procedure for your 7stamp profile during onboarding before enforcing a specific header name or retry policy in production.

Frequently asked questions

Can I select only certain webhook events?

Yes. Select the event types in the 7stamp profile's webhook settings so the receiver gets only the events that matter to its workflow.

How do I connect webhooks to Make or Zapier?

Create the receiving webhook in Make or a Catch Hook in Zapier, copy the generated URL, then paste it into the 7stamp profile's webhook settings and send a test event.

How should I match an event to my CRM contact?

Use External ID and, when present, External Source. These are the identifiers your integration supplied when the card was created or scanned.

Should I assume a signature header or retry timing?

No. Use the current OpenAPI/profile delivery contract and confirm the authentication procedure for your profile during onboarding before hard-coding a header or retry assumption.

Open API reference Make guide Zapier guide REST API guide

Next step

Ready to send the first card event?

Create a receiver, paste its HTTPS URL into the profile, run a disposable scan, and validate the matching External ID before enabling downstream automation.

Open 7stamp Admin Read the API reference