Sign Customiser

Navigation

Dark mode

Customiser languages

Validate publishing a customiser language

Copy page

Dry-run a language publish without promoting anything. The response on the failing paths is exactly the problem the publish would return, including the missing_keys list, so an agent can report precisely what is still needed before committing.

POST/api/v3/customisers/{customiser_id}/languages/{language_code}/validate-publish
POSTValidate publishing a customiser language
POST/api/v3/customisers/{customiser_id}/languages/{language_code}/validate-publish

Validate publishing a customiser language

Dry-run a language publish without promoting anything. The response on the failing paths is exactly the problem the publish would return, including the `missing_keys` list, so an agent can report precisely what is still needed before committing. On a language that would publish, the response is a 200 `customiser_language_validation` confirmation. Nothing is written, no caches are touched, no idempotency key is consumed, and no activity is recorded. The verdict is advisory: nothing binds it to a later publish, and the draft copy can legitimately change between the two calls. Requires the `customisers:write` scope, because it is the write dry-run twin. 401, 403, 404, 409, 422, and 429 problems behave exactly as on the publish operation.

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.

The language tag, from the list customiser languages operation.

Validate publishing a customiser language

Overview

On a language that would publish, the response is a 200 customiser_language_validation confirmation. Nothing is written, no caches are touched, no idempotency key is consumed, and no activity is recorded. The verdict is advisory: nothing binds it to a later publish, and the draft copy can legitimately change between the two calls. Requires the customisers:write scope, because it is the write dry-run twin. 401, 403, 404, 409, 422, and 429 problems behave exactly as on the publish operation.

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

language_codestringpathrequired

The language tag, from the list customiser languages operation.

Example: fr

Validate publishing a customiser language
curl https://web.signcustomiser.com/api/v3/customisers/1/languages/fr/validate-publish \
  --request POST \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer YOUR_API_TOKEN'
Response
{
  "data": {
    "object": "customiser_language_validation",
    "operation": "publish",
    "customiser_id": 42,
    "language_code": "fr",
    "valid": true
  },
  "links": {
    "self": "https://web.signcustomiser.com/api/v3/customisers/42/languages/fr/validate-publish",
    "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.