# Profile evidence

> API type: profile. Reward a participant for completing approved profile attributes.

Source: https://dashboard.adquest.batriders.ir/docs/quest-evidence/profile · Audience: Developers · Section: Quest evidence

## Synchronize profile changes

1. Start the quest and read client.getGrowthStatus(id) to show the participant what is missing.
2. Let the participant edit their profile in your host application. Save and validate it on your backend.
3. Mint a new participant session with the updated authorized host context and update the SDK token.
4. Read growth status again and submit completion once the requirement is met.

**Complete after the server has the updated profile**

```typescript
const status = await client.getGrowthStatus(questId);
// Render status.profile and guide the user through missing fields.
// After saving the profile and refreshing the participant session:
const completion = await questRequest(config, questId, "complete");
```

- [Send host context](https://dashboard.adquest.batriders.ir/docs/participant-sessions#profile-context): Supported fields, permissions and backend session refresh.

## Verify profile eligibility

- Test a partially filled profile, a qualifying profile and a user who declines permission.
- Check that frontend-only field changes do not count before backend synchronization.
- Do not substitute synthetic attributes to satisfy a required field.

## Next steps

- [Quest evidence overview](https://dashboard.adquest.batriders.ir/docs/quest-evidence): The shared request helper and the completion flow.
- [Quest actions API](https://dashboard.adquest.batriders.ir/docs/api/quest-actions): Every request and response.
- [Set up this quest in the dashboard](https://dashboard.adquest.batriders.ir/docs/dashboard/quests/profile): For publishers: configure and publish the quest.