> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/salesforce/agent-assisted-ordering/acquisition-flow/gift-subscription/gift-redeemer-details.md).

# Redeemer Details

**LFS version requirement**: requires Limio for Salesforce version 11.68 or later.

When looking at a subscription that is a gift purchase, details of whether the gift might be redeemed, and redemption related details, aren't available at subscription level.

In the Limio for Salesforce Manage Subscriptions flow, there is a flow apex action that takes the subscription id as an input and, if it's a gift purchase, returns in a custom apex object the following information:

* isRedeemed
* redemptionStatus
* giftCode
* redemptionDate
* expiryDate
* subscriptionId
* accountId
* contactId

<figure><img src="/files/0ASDYyBXeIfhqwSwrinC" alt=""><figcaption></figcaption></figure>

This is implemented by the global apex class 'GiftRedeemerDetails' in the Limio for Salesforce category<br>

<figure><img src="/files/nvxJxzjTXur7N55sTT7X" alt=""><figcaption></figcaption></figure>

The only field that needs to be mapped as input for the selected action is the subscriptionId, that needs to contain the identifier for the gift purchaser subscription.

<figure><img src="/files/mb7J7ydrDcWlCHgAS5Pj" alt=""><figcaption></figcaption></figure>

This class will then output an apex class of type i42as\_\_GiftRedeemer, and its parameters can be used elsewhere in the flow as variable for building custom text, or for building a custom lightning web component displaying this information in a purpose built layout.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.limio.com/salesforce/agent-assisted-ordering/acquisition-flow/gift-subscription/gift-redeemer-details.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.