> ## Documentation Index
> Fetch the complete documentation index at: https://6f524b4-productmetrics.manicule.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.
> For every page in one file, fetch https://6f524b4-productmetrics.manicule.dev/docs/llms-full.txt (large).
> To search and read these docs as tools, connect the MCP server at https://6f524b4-productmetrics.manicule.dev/docs/api/mcp.
> Every agent surface: https://6f524b4-productmetrics.manicule.dev/docs/.well-known/llms-manifest.json

# Reorder product rules (/docs/api/settings/product-rules-reorder)

<!-- agent-signals: reading_time_min: 3 · est_tokens: 1216 · updated: 2026-11-16 -->
Related: [Generate the feed now](/docs/api/settings/feed-generate.md), [Get feed source settings](/docs/api/settings/feed-source-settings-get.md), [Save feed source settings](/docs/api/settings/feed-source-settings-update.md), [Get Product Segmentation settings](/docs/api/settings/get.md), [Get inventory planning settings](/docs/api/settings/inventory-settings-get.md), [Save an inventory planning setting](/docs/api/settings/inventory-settings-update.md)

> Sets the order the property's product rules apply in: send every rule id from product_rules.list with a unique priority (lower applies first).

`PUT https://prod-backend.productmetrics.io/api/public/v1/properties/{propertyId}/product-rules/reorder`

**Scope** `write` · **Access** Changes data · **Operation id** `product_rules.reorder`

## Try it

`productmetrics` runs after `productmetrics login`; curl needs `PM_TOKEN` (see [Authentication](/docs/api/overview#authentication)). Set `$PROPERTY_ID` first.



**productmetrics CLI:**

```bash
productmetrics product-rules reorder \
  --property-id $PROPERTY_ID \
  --rules '[{"id":"6f1c2a7e-3b4d-4e8f-9a01-2c3d4e5f6a7b","priority":1}]' \
  --json
```

**curl:**

```bash
curl -X PUT "https://prod-backend.productmetrics.io/api/public/v1/properties/$PROPERTY_ID/product-rules/reorder" \
  -H "Authorization: Bearer $PM_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "rules": [
      {
        "id": "6f1c2a7e-3b4d-4e8f-9a01-2c3d4e5f6a7b",
        "priority": 1
      }
    ]
  }'
```

## Response

API response (200):

```json
{
  "data": {
    "success": true
  },
  "request_id": "req_01JFAPJAJRSNGW6K1HSK26PVQM"
}
```

**CLI output:** `productmetrics product-rules reorder --json` prints `{ "ok": true, "data": …, "request_id": "…" }` with the same `data`.

## Before you call

A 409 means the rules changed since you listed them: list again and retry. The change reaches the feed at the nightly run, or now with [`feed.generate`](/docs/api/settings/feed-generate). Needs an editor or admin.

## Path parameters

| Name         | Type          | Description                                                           |
| ------------ | ------------- | --------------------------------------------------------------------- |
| `propertyId` | string (uuid) | A property_id from [`properties.list`](/docs/api/account/properties-list). |

## Query parameters

| Name         | Type   | Required | Description                                                                                                            |
| ------------ | ------ | -------- | ---------------------------------------------------------------------------------------------------------------------- |
| `feed_scope` | string | No       | Which feed of the property: a feed id, or `all` for the property-wide settings. Omitted: the property's default scope. |

## Body

| Name               | Type            | Required | Description                                                                    |
| ------------------ | --------------- | -------- | ------------------------------------------------------------------------------ |
| `rules`            | array of object | Yes      | Every rule of the property, each with its `id` and new `priority`.             |
| `rules[].id`       | string (uuid)   | Yes      | The rule's `id` from [`product_rules.list`](/docs/api/settings/product-rules-list). |
| `rules[].priority` | integer         | Yes      | Its place in the order, unique per rule; lower applies first.                  |

## Errors

A failure answers with its HTTP status and `{ error: { code, message, details? }, request_id }`. Branch on `code` (stable, lower_snake); show `message` to the person. The CLI prints the same `error` with `"ok": false`.

```json
{
  "error": {
    "code": "insufficient_scope",
    "message": "This operation needs the write scope; connect again and allow it.",
    "details": {
      "required_scope": "write"
    }
  },
  "request_id": "req_01J3KDEWBY3ZMZ5T8B1W2BHEZ6"
}
```

| Status | Code                 | When                                                                                                                      |
| ------ | -------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| 400    | `invalid_request`    | A path, query or body value does not match this page. `details.issues` lists each `location`, `path` and `message`.       |
| 401    | `invalid_token`      | The token is missing, expired or revoked: sign in again (`productmetrics login`). The `WWW-Authenticate` header says why. |
| 403    | `insufficient_scope` | The token lacks the `write` scope (`details.required_scope`): sign in again and allow it.                                 |
| 404    | `not_found`          | An id in the path does not exist, or the signed-in person cannot open it.                                                 |
| 409    | `conflict`           | A 409 means the rules changed since you listed them: list again and retry.                                                |
| 429    | `rate_limited`       | More than 600 requests a minute for this person: wait the `Retry-After` seconds (60) and retry.                           |

[All Settings and rules operations](/docs/api/settings)
