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.
Developer integration
7stamp Webhooks
AvailablePush 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.
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.
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.
Available events
`card_issued` — A new wallet card was issued.
`card_saved` — The customer saved the card to their wallet.
`card_opened` — The customer opened the card in their wallet.
`stamp_added` — A stamp was added to a card.
`goal_reached` — The customer completed a stamp goal.
`reward_issued` — A reward was issued with type award, voucher, or lottery result.
`voucher_issued` — A voucher was issued.
`voucher_redeemed` — A voucher was redeemed.
`voucher_expired` — A voucher reached its expiry date.
`lottery_played` — The customer played a lottery with a result.
`birthday_reached` — The customer birthday triggered a campaign.
`inactivity_trigger` — The customer hit a win-back inactivity threshold.
`campaign_sent` — A campaign was sent to a segment.
Payload example
{
"event": "voucher_redeemed",
"timestamp": "2026-05-11T12:34:56Z",
"business_id": "b_123",
"location_id": "loc_45",
"customer": {
"id": "c_789",
"wallet_pass_id": "wp_abc",
"language": "en"
},
"card": { "id": "card_001", "goal_index": 2 },
"voucher": {
"id": "v_555",
"type": "voucher",
"redeem_code": "FREECOFFEE",
"redeem_code_formats": ["text", "qr", "barcode"],
"status": "redeemed",
"redeemed_via": "staff_scanner"
}
}How to configure
Open admin.7stamp.com and go to Stamp Cards -> API & Integrations -> Webhooks.
Add your endpoint URL. HTTPS only.
Select the events you want to subscribe to.
Save. Events begin flowing within seconds.
Security
Each webhook payload is signed with HMAC-SHA256. Verify the X-7stamp-Signature header before processing. Endpoints should respond with HTTP 200 within 10 seconds. Failed deliveries are retried with exponential backoff for up to 24 hours.
Frequently asked questions
What is the difference between webhooks and the REST API?
Webhooks push events out of 7stamp in real time. The REST API lets your own software issue cards, add stamps, and create vouchers by calling 7stamp.
Can I choose which events to receive?
Yes. When you configure the webhook endpoint, you choose which event types to subscribe to.
Do I need Zapier or Make to use webhooks?
No. Webhooks work directly with your backend. Zapier and Make are simply no-code wrappers for the same event stream when they launch.
Related pages
Next step
Need loyalty events inside your CRM in real time?
Use webhooks when your team already has a backend or integration layer and wants total control over what happens after each loyalty event.