---
title: "Features overview"
description: "List, check, and activate customer account features."
---

# Features overview

Use the Features API to list available features, check a customer's eligibility, and activate supported capabilities.

<CardGroup cols={2}>
  <Card title="Browse feature endpoints" icon="code" href="/api-reference/features/get-v1-risk-features">
    List available features or browse the operations in this category.
  </Card>
  <Card title="Features integration guide" icon="book" href="/platform/features/overview">
    Learn how feature discovery, eligibility, and activation work.
  </Card>
</CardGroup>

## How it works

Features are capabilities — such as cards, collections, or FX — that are switched on per customer. The lifecycle has three steps:

1. **Discover** — call [`GET /v1/risk/features`](/api-reference/features/get-v1-risk-features). Without a `customer_id` it returns all available features and their requirements; with a `customer_id` it returns that customer's features and their activation status.
2. **Check eligibility** — call [`POST /v1/risk/features/eligibility`](/api-reference/features/post-v1-risk-features-eligibility) to confirm the customer qualifies and see any outstanding requirements.
3. **Activate** — call [`POST /v1/risk/features/activate`](/api-reference/features/post-v1-risk-features-activate) with the `feature_id` and any required `provider_data` from the feature's requirements.

## Endpoints

| Endpoint | Description |
|---|---|
| [`GET /v1/risk/features`](/api-reference/features/get-v1-risk-features) | List available features, or a customer's features and activation status |
| [`POST /v1/risk/features/eligibility`](/api-reference/features/post-v1-risk-features-eligibility) | Check a customer's eligibility for a feature and list its requirements |
| [`POST /v1/risk/features/activate`](/api-reference/features/post-v1-risk-features-activate) | Activate a feature for a customer |

## Authentication

All requests use `https://api.gravv.xyz/v1/` and authenticate with the `Api-Key` header. See [Authentication](/getting-started/authentication) for details.