High-level flow
A typical integration does three things:- Identify the customer. Look up or create a LoyaltyDog customer by email, phone, or a custom identifier.
- Record activity. Post a transaction so the program’s rules credit points or issue rewards.
- Surface state back to the user. Fetch the wallet pass URL, point balance, or gift card balance to display in your UI.
A minimal example
Best practices
- Make calls idempotent. Use your own order or transaction ID in the
referencefield so retries don’t double-credit. - Handle 429s gracefully. Back off when you see rate-limit responses and respect the
Retry-Afterheader. - Subscribe to webhooks. Don’t poll for state changes — let LoyaltyDog notify you. See Webhooks.
- Scope tokens per integration. Use a dedicated app key for each integration so you can rotate or revoke without impacting other systems.
Reference
Full API
Every endpoint, request, and response schema.
Authentication
Bearer tokens, app keys, and rotation.
Webhooks
Real-time event delivery.
MCP server
For AI-assistant-driven integrations.
