# List your notifications

```http
GET https://secure.yoprint.com/v1/api/store/{team_slug}/current_user_feed
```

- API version: v1
- Operation ID: `v1_public_current_user_feed_index`
- Section: Messages and activity › [Notifications](https://developer.yoprint.com/reference/notifications.md)
- Web page: https://developer.yoprint.com/reference/notifications/v1-current-user-feed-index/
- Authentication: `Authorization: Bearer YOUR_API_KEY`

Lists your notifications on this team, newest first: activity that concerns you, such as new comments, customer replies, payments received and approvals answered.

**By default only unseen, unarchived items are returned.** Send `not_seen_yet=0` to include seen items, and `show_archive=1` to include archived ones too (it adds them; it does not return only archived items). The page size is your team's list size setting (50 unless changed).

Customer Portal payment notifications (`type` `customer_payment`) are listed only when your role may see that customer's finances; others are left out of the page and of the total.

## Permission

Your own feed only: the key's owner. Payment notifications need more, see the rules.

## Business rules

- `not_seen_yet` and `show_archive` take `1` or `0`. `true` and `false` are refused.
- A `customer_payment` notification is listed for the team owner, or for a role with View Customer Sales Aggregates and Manage Customers ("Manage All", or "Manage Assigned to User" when the customer is assigned to you). Its `payment.affected_orders` lists only the orders you may see, and none without View Sales Order Pricing.
- Access is checked again for each row: if you lose access after a payment notification was listed, it comes back with `action` `payment_access_changed`, `message_key` `customer_payment.payment_access_changed` and `object` `[]`.
- A key whose user is no longer a member of the team gets an empty list.

## Path parameters

- `team_slug` (string, required): Your team slug, shown as Team ID next to your API key in Profile. Example `your-team`.

## Query parameters

- `not_seen_yet` (integer, optional): `1` (default): only unseen items. `0`: seen and unseen. One of: `0`, `1`. Default `1`. Example `0`.
- `show_archive` (integer, optional): `0` (default): leave out archived items. `1`: include them. One of: `0`, `1`. Default `0`. Example `0`.
- `page` (integer, optional): Default `1`. Minimum 1.

## Request body

This operation takes no request body.

### Example request

```bash
curl 'https://secure.yoprint.com/v1/api/store/your-team/current_user_feed' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Accept: application/json' \
  -H 'X-Yoprint-Decimal-Format: exact-v1'
```

## Response

`200` Successful response.

Fields:

- `data` (array of objects, required)
  - Each item:
    - `activity` (object, optional): What happened.
      - `action` (string, optional): What happened. For `customer_payment`: `dispute_opened`, `dispute_under_review`, `dispute_won`, `funds_withheld`, `chargeback_confirmed`, `payment_reversed`, `payment_needs_attention`, `deadline_approaching`, `deadline_overdue`, `funds_released`, `funds_restored`, `case_won_awaiting_funds`, `payment_resolved`, `provider_refund_applied` or `provider_refund_failed`; `payment_access_changed` when you can no longer see that payment.
      - `created_at` (string (date-time), optional)
      - `id` (string, optional)
      - `message_key` (string, optional): Identifies the kind of notification, for your own wording: `<type>.<action>`, such as `order.new_comment`.
      - `object` (object | array, optional): The details, which depend on the kind: for example the order, the comment and who wrote it (`user`: `id`, `name`, `avatar_url`). An empty array `[]` when there are none. For `customer_payment`, the payment as it was then (`payment`, with the orders it touched in `payment.affected_orders`, limited to the ones you may see); `[]` when you can no longer see that payment.
      - `team` (object, optional)
        - `id` (string, optional)
        - `name` (string, optional)
        - `slug` (string, optional)
      - `type` (string, optional): What the notification is about, such as `order`. `customer_payment` for Customer Portal payment events (disputes, chargebacks, refunds and holds).
    - `archive` (boolean, optional)
    - `created_at` (string (date-time), optional)
    - `id` (string, optional): The feed item id. Use it with the mark operations.
    - `seen` (boolean, optional)
- `status` (integer, required)
- `success` (boolean, required)
- `pagination` (object, optional)
  - `count` (integer, required)
  - `currentPage` (integer, required)
  - `links` (object | array of any, required): Links to the neighbouring pages: `previous` and `next`, each present only when that page exists. An empty list, `[]`, when there is only one page.
    - `next` (string (uri), optional): The next page.
    - `previous` (string (uri), optional): The previous page.
  - `perPage` (integer, required)
  - `total` (integer, required)
  - `totalPages` (integer, required)

Example response:

```json
{
  "data": [
    {
      "activity": {
        "action": "new_comment",
        "created_at": "2026-11-03T09:30:00+00:00",
        "id": "r5rAJkp7z5ZNZI",
        "message_key": "order.new_comment",
        "object": {
          "comment": {
            "comment": "Customer approved the blue ink.",
            "id": "JiDNJJ08el0QrD"
          },
          "order": {
            "id": "V4keXwwxMQyXw7",
            "object_type": "sales_order",
            "quote": false,
            "scoped_id": "SO1001"
          },
          "team": {
            "id": "1ulms05RCQN3k2",
            "name": "Example Print Shop"
          },
          "user": {
            "avatar_url": "https://example.com/avatar.png",
            "id": "VG7s3tFzyQbO2N",
            "name": "Alex Rivera"
          }
        },
        "team": {
          "id": "OwgPxM73OKqou3",
          "name": "Example Print Shop",
          "slug": "your-team"
        },
        "type": "order"
      },
      "archive": false,
      "created_at": "2026-11-03T09:30:00+00:00",
      "id": "H3w5wUZaIrCb52",
      "seen": false
    }
  ],
  "pagination": {
    "count": 1,
    "currentPage": 1,
    "links": [],
    "perPage": 50,
    "total": 1,
    "totalPages": 1
  },
  "status": 200,
  "success": true
}
```

## Errors

- `401` The API key is missing or wrong (`unauthenticated`).
- `403` You are not allowed to do this. `api_access_not_in_plan`: your team's plan doesn't include API access (Pro and above, with an active subscription or trial), so every request answers this until the team upgrades. When your role lacks the permission the operation needs, the body is only `{"message": "Insufficient Permission"}`. Other refusals use the error envelope, with `unauthorized` or `user_is_not_authorized`.
- `404` Not found. `page_not_found`: the team slug is unknown, you are not a member of the team, or an id in the path is not one of this team's. `code: null`, with a message that starts "No query results for": there is no record with that id.
- `422` The request was refused and changed nothing. `validation_failed` lists what to fix in `error.fields`; other codes name a business rule, explained in `error.message`. A few checks answer with only `{"message": "..."}`. An operation that calls another service (a payment provider, a carrier, an accounting app) can answer `connect_timeout` ("Please retry again") when that service does not answer in time: the change may or may not have happened there, so read the record back before you retry.
  - When: `not_seen_yet` or `show_archive` is not `0` or `1` (`validation_failed`; `error.fields` names the field). Fix: Send `1` or `0`.

## Related

- [Mark notifications as seen](https://developer.yoprint.com/reference/notifications/v1-current-user-feed-seen.md): `PUT /v1/api/store/{team_slug}/current_user_feed/seen`
- [Mark all your notifications as seen](https://developer.yoprint.com/reference/notifications/v1-current-user-feed-mark-all-as-seen.md): `PUT /v1/api/store/{team_slug}/current_user_feed/mark_all_as_seen`
- [Archive notifications](https://developer.yoprint.com/reference/notifications/v1-current-user-feed-archive.md): `PUT /v1/api/store/{team_slug}/current_user_feed/archive`