Skip to content
Settings and rules

Reorder product rules

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 /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). Set $PROPERTY_ID first.

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

Response

API response (200):

{
  "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. Needs an editor or admin.

Path parameters

NameTypeDescription
propertyIdstring (uuid)A property_id from properties.list.

Query parameters

NameTypeRequiredDescription
feed_scopestringNoWhich feed of the property: a feed id, or all for the property-wide settings. Omitted: the property’s default scope.

Body

NameTypeRequiredDescription
rulesarray of objectYesEvery rule of the property, each with its id and new priority.
rules[].idstring (uuid)YesThe rule’s id from product_rules.list.
rules[].priorityintegerYesIts 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.

{
  "error": {
    "code": "insufficient_scope",
    "message": "This operation needs the write scope; connect again and allow it.",
    "details": {
      "required_scope": "write"
    }
  },
  "request_id": "req_01J3KDEWBY3ZMZ5T8B1W2BHEZ6"
}
StatusCodeWhen
400invalid_requestA path, query or body value does not match this page. details.issues lists each location, path and message.
401invalid_tokenThe token is missing, expired or revoked: sign in again (productmetrics login). The WWW-Authenticate header says why.
403insufficient_scopeThe token lacks the write scope (details.required_scope): sign in again and allow it.
404not_foundAn id in the path does not exist, or the signed-in person cannot open it.
409conflictA 409 means the rules changed since you listed them: list again and retry.
429rate_limitedMore than 600 requests a minute for this person: wait the Retry-After seconds (60) and retry.

All Settings and rules operations