DELETE
Delete file types
Request · Response · Guide: Extract fields
Each id is processed independently. The endpoint returns HTTP 200 whenever the request is authorized and the body is valid, even when some or all ids fail — per-id failures are reported in errors[], and success is false only when nothing was deleted and at least one id failed.Deleting an id that was already deleted yields a per-item “Schema is not found or already deleted” error rather than a request-level failure, so retries are safe.Malformed ids are reported as per-item Invalid schema ID format errors, not as a validation failure for the whole request. Duplicate ids are processed once.An id that fails for an unexpected reason reports the generic message Schema could not be deleted; the underlying cause is recorded server-side.At most 50 ids may be sent per request; a larger batch is rejected with 422 VALIDATION_FAILED before any deletion runs. Deletion is performed inline and one id at a time, so split larger sets across requests.The Idempotency-Key header is optional. When supplied, a repeated request with the same key replays the original response for 24 hours.

Authorizations

x-api-key
string
header
required

API key for authentication

Headers

Idempotency-Key
string

Optional opaque key (max 255 chars, UUIDv4 recommended) making this request idempotent for 24h: a retry with the same key and body replays the original response with Idempotent-Replayed: true.

Body

application/json
blueprintIds
string[]
required

File type ids to delete, at most 50 per request. Repeated ids are collapsed and processed once. A malformed id is reported in errors rather than failing the request.

Required array length: 1 - 50 elements
Example:

Response

The delete request was processed; inspect the payload for per-id outcomes

success
boolean
deletedCount
number
failedCount
number
errors
object[]