Sign Customiser

Dry-runs POST/api/v3/uploads with the same body. Returns the same problem the create would return, or a verdict saying it would succeed.

POST/api/v3/uploads/validate-create

Overview

Requires customisers:write. Nothing is created, no target is minted, no idempotency key is consumed, and no budget is spent.

Authorisation

Bearer token required. Include it in theAuthorization header.

Required scope: customisers:write

Request body

purposestringbody
filenamestringbody
content_typestringbody
byte_sizeintegerbody

Request body example

application/json
{
  "purpose": "font_ttf",
  "filename": "Signature.ttf",
  "content_type": "font/ttf",
  "byte_size": 184320
}
Validate an upload create
curl https://web.signcustomiser.com/api/v3/uploads/validate-create \
  --request POST \
  --header 'Accept: application/json' \
  --header 'Authorization: Bearer YOUR_API_TOKEN' \
  --header 'Content-Type: application/json' \
  --data '{
  "purpose": "font_ttf",
  "filename": "Signature.ttf",
  "content_type": "font/ttf",
  "byte_size": 184320
}'
Response
{
  "data": {
    "object": "upload_validation",
    "operation": "create",
    "purpose": "font_ttf",
    "valid": true
  },
  "links": {
    "self": "https://web.signcustomiser.com/api/v3/uploads/validate-create",
    "documentation": "https://www.signcustomiser.com/help/api/"
  },
  "meta": {
    "api_version": "v3",
    "request_id": "req_01jz9x2k7c8f3m5n6p7q8r9s0t"
  }
}