# My benefits (https://docs.loybox.com.ar/en/api-reference/mi-cuenta/mis-beneficios)



<Endpoint method="GET" path="/v1/me/benefits" auth="user-token" />

Benefits the user already bought with their points at this commerce and can still
redeem.

Each item's `client_benefit_code` is the code the user presents at the commerce to
redeem it.

## Headers
<Fields>
  <Field name="X-Commerce-Id" type="integer" location="header" required="true">
    Id of the commerce integrating the API. Every response is scoped to this
    commerce.
  </Field>
</Fields>

## Response
An array of
[Redeemable benefit](https://docs.loybox.com.ar/api-reference/objetos#beneficio-canjeable).

```bash
curl https://loybox-public-api-752998171300.southamerica-west1.run.app/v1/me/benefits \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "X-Commerce-Id: 87"
```

```json
// 200 OK
[
  {
    "client_benefit_code": 887766,
    "issue_date": "2026-08-24T13:05:00Z",
    "due_date": "2026-09-23T13:05:00Z",
    "used": false,
    "benefit": {
      "id": "b_9f2a",
      "type": "percentage_discount",
      "description": "20% de descuento en toda la tienda",
      "cost": 250,
      "expiration": "2026-12-31T23:59:59Z",
      "benefit_type": "normal",
      "color": "#f1a10d",
      "buy_limit": 0,
      "prize": null,
      "tiendanube_coupon": null
    }
  }
]
```

<Callout title="The code is the coupon">
  In an online store, the `client_benefit_code` is what the user pastes at checkout.
  It is worth showing it large and with a copy button, and the `due_date` next to it
  so they know how long they have to use it.
</Callout>

## Errors
| Code  | When                                                                     |
| ----- | ------------------------------------------------------------------------ |
| `401` | The access token is missing, expired, or does not belong to an end user. |
| `422` | The `X-Commerce-Id` header is missing.                                   |
