Sign Customiser

Dry-runs the activation without changing anything: a customiser the store's plan has no room for returns the identical 422 activation_not_allowed problem the activation would return, and one that can go live returns a 200 verdict whose will_be_active is true. Nothing is written and no idempotency key is consumed.

POST/api/v3/customisers/{customiser_id}/validate-activate

Overview

The verdict is advisory — the store's live slots can change between the two calls. Requires customisers:write.

Authorisation

Bearer token required. Include it in theAuthorization header.

Required scope: customisers:write

Path parameters

customiser_idstringpathrequired

The customiser id.

Example: 1

Validate a customiser activation
curl https://web.signcustomiser.com/api/v3/customisers/1/validate-activate \
  --request POST \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer YOUR_API_TOKEN'
Response
{
  "data": {
    "object": "customiser_validation",
    "operation": "activate",
    "customiser_id": 42,
    "will_be_active": true,
    "valid": true
  },
  "links": {
    "self": "https://web.signcustomiser.com/api/v3/customisers/42/validate-activate",
    "documentation": "https://www.signcustomiser.com/help/api/"
  },
  "meta": {
    "api_version": "v3",
    "request_id": "req_01jz9x2k7c8f3m5n6p7q8r9s0t"
  }
}