Sign Customiser

Navigation

Dark mode

Customiser sections

Validate a icons section update

Copy page

Dry-run a icons section merge patch without persisting anything. The request body is the same merge patch the update operation accepts, and on the failing paths the response is exactly what that update would produce: the identical 422 problem, because the same validation code path runs and only persistence is skipped.

POST/api/v3/customisers/{customiser_id}/icons-section/validate-update
POSTValidate a icons section update
POST/api/v3/customisers/{customiser_id}/icons-section/validate-update

Validate a icons section update

Dry-run a icons section merge patch without persisting anything. The request body is the same merge patch the update operation accepts, and on the failing paths the response is exactly what that update would produce: the identical 422 problem, because the same validation code path runs and only persistence is skipped. On a patch that would apply, the response is a 200 `icon_section_validation` confirmation. Nothing is written, no caches are touched, no idempotency key is consumed, and no activity is recorded, so the operation is always safe to repeat. The verdict is advisory: nothing binds it to a later update, and the section can change between the two calls. Requires the `customisers:write` scope (it is the write's dry-run twin). A 400 problem means the body is not valid JSON; a 422 problem with code `invalid_document` means the body is not a JSON object. 401/403/404/429 behave as on the read operation, with `customisers:write` as the required scope.

Authorisation

The Authorization header expects a Bearer token. Generate one on the API keys page in your dashboard.

Path

The customiser id, from the list customisers operation.

Body
Validate a icons section update

Overview

On a patch that would apply, the response is a 200 icon_section_validation confirmation. Nothing is written, no caches are touched, no idempotency key is consumed, and no activity is recorded, so the operation is always safe to repeat. The verdict is advisory: nothing binds it to a later update, and the section can change between the two calls. Requires the customisers:write scope (it is the write's dry-run twin). A 400 problem means the body is not valid JSON; a 422 problem with code invalid_document means the body is not a JSON object. 401/403/404/429 behave as on the read operation, with customisers:write as the required scope.

Authorisation

Bearer token required. Include it in the Authorization header.

Required scope: customisers:write

Path parameters

customiser_idstringpathrequired

The customiser id, from the list customisers operation.

Example: 1

Request body

titlestringbody
descriptionstringbody

Request body example

application/json
{
  "title": "Choose your icon",
  "description": "Pick one of our icons."
}
Validate a icons section update
curl https://web.signcustomiser.com/api/v3/customisers/1/icons-section/validate-update \
  --request POST \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer YOUR_API_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
  "title": "Choose your icon",
  "description": "Pick one of our icons."
}'
Response
{
  "data": {
    "object": "icon_section_validation",
    "operation": "update",
    "customiser_id": 42,
    "valid": true
  },
  "links": {
    "self": "https://web.signcustomiser.com/api/v3/customisers/42/icons-section/validate-update",
    "documentation": "https://www.signcustomiser.com/help/api/"
  },
  "meta": {
    "api_version": "v3",
    "request_id": "req_01jz9x2k7c8f3m5n6p7q8r9s0t"
  }
}

Type a question and press Enter. Use the arrow keys to move between the results.