Perksmith · developers
Build the connection. Keep the customer in view.
Connect Perksmith Rewards to your website or app, from customer identification to checkout and the next interaction. The developer documentation covers the API operations, data formats and setup your team needs.
Follow the purchase from first request to final record.
Map the customer, purchase context, reward decision and confirmation. Include cancellations and refunds so the integration handles a changed purchase as clearly as a successful one. Agree which system owns each action and how both systems recognize the same purchase.
A retry should not become a second reward.
Use the documented authentication and business-account context to keep requests within the right business. Keep credentials out of browser code. Follow the idempotency contract: use a stable request key so retrying a balance change or reward application does not repeat its effect.
When a reward is refused, handle that outcome explicitly. A local discount should not silently override the program’s decision.
Connect the events as well as the checkout.
Use the maintained webhook reference for verification, delivery and recovery behavior. Include delayed and repeated events in your testing. Check the resulting customer balance and purchase record, not only the response status.
Choose the right integration route.
API access, connectors and channels depend on your plan and supported systems. Reward Desk is a different route: staff operate the rewards process alongside their existing billing. Discuss that distinction before deciding what to automate.
Integration questions.
Where is the API reference?
Request integration documentation for the maintained endpoint definitions and examples.
Does keeping a POS mean it is already connected?
No. Confirm a supported integration or use the explicit Reward Desk process.
Everyday sales. Lasting relationships.