# List account determination rules

Operation ID: `accountDeterminationRules`

Group: Inventory › Account Determination Rules

[Open in the interactive reference](https://docs.api.lensing.ai/lensing/v1/endpoints/accountDeterminationRules)

`GET /inventory/account-determination-rules`

Read-only: Reads and returns; changes nothing.

Lists account determination rules, with their names, priorities, and status only.

For their dimensions, accounts, and reason-code overrides, or to filter by them, use POST inventory/account-determination-rules/search.

## Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `Api-Version` | header | string · v1 | yes | The API version this request targets, named by its public identifier. Required on every request; omitting it, or naming a version this company does not have, is answered with 400. This document describes version `v1`. |

## Query surface

- `id` — filter by eq, ne, gt, gte, lt, lte, in, notIn, between, like
- `priority` — filter by eq, ne, gt, gte, lt, lte, in, notIn, between
- `isActive` — filter by eq, ne, gt, gte, lt, lte, in, notIn, between
- `lastModifiedDate` — filter by eq, ne, gt, gte, lt, lte, in, notIn, between
- Orderable: id, ruleName, priority, isActive, lastModifiedDate
- Selectable: id, ruleName, priority, isActive, lastModifiedDate
- `page[size]` — Page size
- `page[cursor]` — Opaque continuation cursor

## Response

`200` Success

Under `data`, an array of accountDeterminationRulesRow:

| Field | Type | Required | Filter | Sort | Description |
| --- | --- | --- | --- | --- | --- |
| `id` | string | no | Exact (`eq`, `ne`), Range (`gt`, `gte`, `lt`, `lte`, `between`), Any of (`in`, `notIn`), Pattern (`like`) | yes | The unique identifier for the rule. Format: UUID. Example: `"8d3f1a60-4c27-4e95-b013-6f2a89d47c5e"`. |
| `ruleName` | string | no | no | yes | The name of the rule. It does not have to be unique. Example: `"Finished goods — receipts"`. |
| `priority` | number \| null | no | Exact (`eq`, `ne`), Range (`gt`, `gte`, `lt`, `lte`, `between`), Any of (`in`, `notIn`) | yes | The priority of the rule. When two matching rules are equally specific, the one with the lower number is used. A rule with no `priority` counts as 0. Example: `10`. |
| `isActive` | boolean \| null | no | Exact (`eq`, `ne`), Range (`gt`, `gte`, `lt`, `lte`, `between`), Any of (`in`, `notIn`) | yes | Whether the rule is active. Example: `true`. |
| `lastModifiedDate` | date-time \| null | no | Exact (`eq`, `ne`), Range (`gt`, `gte`, `lt`, `lte`, `between`), Any of (`in`, `notIn`) | yes | The date and time the rule last changed, in UTC. Format: YYYY-MM-DDTHH:mm:ss.sssZ. Requests that change only the reason-code overrides do not update this field. Example: `"2026-05-12T09:30:00.000Z"`. |

```json
{
  "data": [
    {
      "id": "8d3f1a60-4c27-4e95-b013-6f2a89d47c5e",
      "ruleName": "Finished goods — receipts",
      "priority": 10,
      "isActive": true,
      "lastModifiedDate": "2026-05-12T09:30:00.000Z"
    }
  ],
  "pagination": {
    "hasMore": true,
    "nextCursor": "<nextCursor>"
  }
}
```

## Statuses

- `400` — Invalid request or business failure
- `401` — The request carries no valid access token.
- `403` — Not authorized
- `404` — Not found
- `429` — Too many requests from this client address. The response has no body and no `Retry-After` header.
- `500` — Internal server error