FAQs
How do I authenticate?
Section titled “How do I authenticate?”Send your server-side tenant API key in the x-api-key header. There is no login
endpoint or access-token refresh flow. Use GET /b2b/whoami to verify the key.
What should I do after a purchase timeout?
Section titled “What should I do after a purchase timeout?”Retry POST /b2b/purchases with the exact same Idempotency-Key and request body.
The service returns the original result when the first request succeeded. Do not use
a new key until you know the original request was rejected before creation.
How do I know that a purchase is complete?
Section titled “How do I know that a purchase is complete?”Read GET /b2b/purchases/{orderId}. The current B2B v1 contract has no outbound
webhooks. A fulfilled purchase can contain fulfillment credentials or a portal
coupon; protect those fields as sensitive data.
Should I cache the catalog?
Section titled “Should I cache the catalog?”You may cache it briefly for display, but refresh before a purchase and after a
validation_error. Offer pricing and denomination rules are tenant-specific.
Can I put the API key in a mobile app or WebView?
Section titled “Can I put the API key in a mobile app or WebView?”No. Call RewardOS from your server. For streak UI, mint a short-lived embed URL on your server and send only that URL to the WebView or iframe.
How do I top up the wallet?
Section titled “How do I top up the wallet?”Wallet funding is arranged through RewardOS support. The B2B API exposes read-only balance and ledger endpoints; it has no self-service top-up endpoint.