> For the complete documentation index, see [llms.txt](https://docs.subs.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.subs.fun/help/redeeming-invite.md).

# Redeeming invite

## iOS

If you received an invite, you should have a Subs Testflight link.

In order to download Subs, you need to first have the [Apple Testflight app](https://apps.apple.com/us/app/testflight/id899247664).

Once you've downloaded the Apple Testflight app, open the Subs Testflight link on your iPhone.

This should prompt you to install the **Subs: Trade Your Interests beta** app.

Open the Subs app, and go through the sign up flow.

* If you sign up through email, you will receive a code to your email from Privy.
* If you sign up through X, you will need to authorize the connection.

After this step (not before), you will be prompted for your Subs invite code.

## Android

[Subs on the Google Play store](https://play.google.com/store/apps/details?id=fun.subs.app)

Open the Subs app, and go through the sign up flow.

* If you sign up through email, you will receive a code to your email from Privy.
* If you sign up through X, you will need to authorize the connection.

After this step (not before), you will be prompted for your Subs invite code.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.subs.fun/help/redeeming-invite.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
