1
Get an Org-API-Key
Create a developer account and a sandbox key in the
developer portal. The key is a server-side
secret - keep it on your backend.
2
Install an SDK
3
Mint a member token from your backend
The app never holds the Org-API-Key. Your backend exchanges it for a
short-lived member token scoped to one of your users:The response is a
TokenGrant - an accessToken and an expiresAt. Hand the
accessToken to the app. See Authentication for the full
refresh contract.4
Browse and redeem
Initialize the SDK with the member token and run the data flow - check
eligibility, list offers, and redeem the first one:Run it with the member token in the environment:
A successful run prints the member’s tier and balance, the number of offers
browsed, and a new redemption id with its status. If a redemption already
exists for that offer, the SDK raises a
REDEMPTION_ALREADY_EXISTS conflict -
see Errors.Next steps
Authentication and refresh
The two-token model and how the SDK refreshes member tokens.
Environments
How sandbox and live differ, and how the key selects one.
Redemptions
Points spend, idempotency, and the redemption lifecycle.
Errors and retries
The error taxonomy, stable codes, and retry behavior.