# Card Program Terms

> Coming soon, upon request — this feature is turned on for your tenant by the Aurea team. [Contact us](https://www.aureahub.com/contact)

The terms the user is asked to accept, with whether each one is.

## Overview

- `terms`: one entry per term, with its `type` and `accepted`. Onboarding needs `general-tos` and `privacy-policy`; a card needs `card-issuer-tos`; `cashback-tos` is the cashback programme's.
- Accept with [Accept Terms](https://docs.aureahub.com/docs/cards-terms-accept.md). Inside the card program session; the answer is the card program's.
- **Illustrative example.** The card program's answer is passed through unchanged and may carry fields not listed here: the example shows only the fields Aurea or its own app reads. Ignore the fields you do not know.

## Endpoint

### `GET /v1/gnosis/user/terms`

Authentication: bearer token required.

The card program's terms and whether the user accepted each.

**Responses**

`200` OK (illustrative)

```json
{
  "terms": [
    { "type": "general-tos", "accepted": true },
    { "type": "privacy-policy", "accepted": true },
    { "type": "…", "typeNeutral": "card-issuer-tos", "accepted": false }
  ]
}
```

**Example request**

```bash
curl https://api.aureahub.com/v1/gnosis/user/terms \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN"
```

---

Web version: https://docs.aureahub.com/#cards-terms-get