Sign Customiser

Dry-runs the create without creating anything: the same body, the same prototype checks, and the same problems the create would return, or a 200 verdict when it would succeed. The verdict carries will_be_active, the activation-quota answer the create would apply, so an agent can tell a merchant in advance whether the new customiser goes live.

POST/api/v3/customisers/validate-create

Overview

Nothing is written, no idempotency key is consumed, and no option-write budget is spent, so the operation is always safe to repeat. The verdict is advisory — nothing binds it to a later create, and 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

Request body

prototypestringbody
namestringbody

Request body example

application/json
{
  "prototype": "neon-frame-fit",
  "name": "Neon sign builder"
}
Validate a customiser create
curl https://web.signcustomiser.com/api/v3/customisers/validate-create \
  --request POST \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer YOUR_API_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
  "prototype": "neon-frame-fit",
  "name": "Neon sign builder"
}'
Response
{
  "data": {
    "object": "customiser_validation",
    "operation": "create",
    "customiser_id": null,
    "prototype": "neon-frame-fit",
    "will_be_active": true,
    "valid": true
  },
  "links": {
    "self": "https://web.signcustomiser.com/api/v3/customisers/validate-create",
    "documentation": "https://www.signcustomiser.com/help/api/"
  },
  "meta": {
    "api_version": "v3",
    "request_id": "req_01jz9x2k7c8f3m5n6p7q8r9s0t"
  }
}