API reward delivery methods

Choosing a delivery method with the Giftbit API

Delivery at a glance

Giftbit's API supports three ways to deliver rewards to recipients: link-based delivery, Giftbit-sent email, and in-app embedding.

The choice comes down to whether you need pre-built features like setting a claim-by date, or offering choice, and who handles the "last mile" of getting the reward in front of your recipient.

Giftbit email

Lowest effort

Pass the recipient's email, Giftbit sends the reward. Handle branding, resends, and delivery. Trackable from the dashboard or API.

Email is compatible with promotional (setting a claim-by date) and choice formats. Choose this if you want the shortest path to production, or email is your natural channel.

You control branding and content, but not the infrastructure.

Link-based

Maximum control

The API returns a unique reward link. Your system delivers it however you want: your own email templates, SMS, in-app messages, a Slack bot…(the options are endless).

Links are Compatible with promotional (claim period) and choice formats. Choose this if you own the recipient relationship and want full control of the reward experience.

You control everything after the link.

In-app

Embedded experience

Embed reward redemption directly inside your own product.

This option is not compatible with promotional (setting a claim-by date) or choice formats, however you can build a custom choice step in your app. Choose this if recipients are already in your app and you never want them to leave it.

You control the entire redemption surface.