Sign Customiser

Navigation

Dark mode

Customiser languages

Validate cancelling an AI translation

Copy page

Dry-run an AI translation cancel without stopping anything. The response on the failing path is exactly the ai_translation_not_cancellable problem the write would return, with the same reason.

POST/api/v3/customisers/{customiser_id}/languages/{language_code}/validate-cancel-ai-translation
POSTValidate cancelling an AI translation
POST/api/v3/customisers/{customiser_id}/languages/{language_code}/validate-cancel-ai-translation

Validate cancelling an AI translation

Dry-run an AI translation cancel without stopping anything. The response on the failing path is exactly the `ai_translation_not_cancellable` problem the write would return, with the same `reason`. On a translation that would cancel, the response is a 200 `customiser_language_validation` confirmation. Nothing is written, no provider batch is touched, no idempotency key is consumed, and no activity is recorded. The verdict is advisory: nothing binds it to a later cancel, and a running translation can legitimately finish between the two calls. Requires the `customisers:write` scope, because it is the write dry-run twin. 401, 403, 404, 422, and 429 problems behave exactly as on the cancel 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 cancelling an AI translation

Overview

On a translation that would cancel, the response is a 200 customiser_language_validation confirmation. Nothing is written, no provider batch is touched, no idempotency key is consumed, and no activity is recorded. The verdict is advisory: nothing binds it to a later cancel, and a running translation can legitimately finish between the two calls. Requires the customisers:write scope, because it is the write dry-run twin. 401, 403, 404, 422, and 429 problems behave exactly as on the cancel 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 cancelling an AI translation
curl https://web.signcustomiser.com/api/v3/customisers/1/languages/fr/validate-cancel-ai-translation \
  --request POST \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer YOUR_API_TOKEN'
Response
{
  "data": {
    "object": "customiser_language_validation",
    "operation": "cancel",
    "customiser_id": 42,
    "language_code": "fr",
    "valid": true
  },
  "links": {
    "self": "https://web.signcustomiser.com/api/v3/customisers/42/languages/fr/validate-cancel-ai-translation",
    "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.