> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/integrations/integrating-perkville/integrating-your-app-with-perkville/challenges-page/challenge-details-page.md).

# Challenge details page

To provide customers with information about a specific challenge, you can create a Challenge Details page within your mobile app.

#### Accessing Challenge Details

To retrieve the necessary information for a specific challenge, utilize the following endpoints:

1. [**Challenge Perk Requirement Endpoint**](https://www.perkville.com/developers/docs/v2/#v2_resource_6_anchor): This endpoint provides detailed specific actions or activities that must be completed in the challenge.
2. [**Challenge Connection Requirement Summary Endpoint**](https://www.perkville.com/developers/docs/v2/#v2_resource_5_anchor): Challenge Connection Requirement Summary shows a user’s progress on each individual activity for a challenge, and whether they’ve completed this activity.

#### Displaying requirement rewards

The Challenge Perk Requirement response includes:

| Field                        | Meaning                                                                                                              |
| ---------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| `completion_points`          | Points configured for completing the requirement; `0` when no points are configured.                                 |
| `completion_instant_rewards` | A list of active instant reward perk URIs configured for completing the requirement; empty when none are configured. |

Both fields can be populated. Display these rewards with their individual requirement, separately from the final challenge completion reward. Resolve the instant reward perk URIs to obtain the reward details your interface needs.

These are read-only configuration fields. Configure milestone rewards in the business's challenge settings.

#### Distinguishing progress from reward receipt

Use the Challenge Connection Requirement Summary for the customer's progress, and the Challenge Connection for their enrollment state. A completed requirement alone does not establish that the customer received its reward.

* Customers must be enrolled and complete the requirement to earn a milestone reward.
* For a completed requirement when the customer has not joined, show a join prompt rather than a reward-received indicator.
* `completion_points` and `completion_instant_rewards` describe the configured reward. They are not payout status or voucher-delivery confirmation.
* A challenge completion date is the date of completion, not proof of reward delivery.

Continue recording qualifying activity against the requirement's `progress_perk`. Do not create a separate reward transaction from the client: Perkville handles milestone issuance.

See [Challenge Rewards](https://docs.perkville.com/features/settings/challenges/challenge-rewards.md) for the distinction between milestone, final completion, and participation rewards.

#### Example challenge screen

<figure><img src="https://2181708597-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSiE75SeColbiBVbet0NZ%2Fuploads%2FgAAZcPhXSjUM1TIvuCQ7%2Fchallenge-details-milestone-example.jpg?alt=media" alt="Illustrative Fall fitness challenge showing a completed five-class milestone with 25 points and a free smoothie, check-in progress at five of ten, an incomplete personal training requirement, and a locked final reward of 100 points and a free week of training." width="610"><figcaption><p>Illustrative example using the current challenge UI. Requirement rewards appear beside their goals; the trophy section shows the separate final completion reward.</p></figcaption></figure>


---

# 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.perkville.com/integrations/integrating-perkville/integrating-your-app-with-perkville/challenges-page/challenge-details-page.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.
