Sign Customiser

Dry-runs the delete without removing anything: an in-use mounting returns the identical 409 resource_in_use problem the delete would return, and a deletable one returns a 200 verdict. Nothing is written and no idempotency key is consumed.

POST/api/v3/customisers/{customiser_id}/mountings/{mounting_id}/validate-delete

Overview

The verdict is advisory. 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

mounting_idstringpathrequired

The mounting id.

Example: 8

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