Sign Customiser

Customiser length pricings

Validate a length pricing update

Copy page

Dry-runs the merge patch without persisting anything, returning the same problems the update would return or a 200 verdict when it would succeed. Nothing is written, no caches are touched, and no idempotency key is consumed.

POST/api/v3/customisers/{customiser_id}/length-pricings/{length_pricing_id}/validate-update

Overview

The verdict is advisory. Requires pricing:write.

Authorisation

Bearer token required. Include it in theAuthorization header.

Required scope: pricing:write

Path parameters

customiser_idstringpathrequired

The customiser id.

Example: 1

length_pricing_idstringpathrequired

The length pricing id.

Example: 1

Request body

namestringbody

Request body example

application/json
{
  "name": "Standard"
}
Validate a length pricing update
curl https://web.signcustomiser.com/api/v3/customisers/1/length-pricings/1/validate-update \
  --request POST \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer YOUR_API_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
  "name": "Standard"
}'
Response
{
  "data": {
    "object": "length_pricing_validation",
    "operation": "update",
    "customiser_id": 42,
    "length_pricing_id": 9,
    "valid": true
  },
  "links": {
    "self": "https://web.signcustomiser.com/api/v3/customisers/42/length-pricings/9/validate-update",
    "documentation": "https://www.signcustomiser.com/help/api/"
  },
  "meta": {
    "api_version": "v3",
    "request_id": "req_01jz9x2k7c8f3m5n6p7q8r9s0t"
  }
}