Skip to main content
POST
Delete mapping schema

Restrictions

Usage

  • If the schema is still referenced, the response returns HTTP 400 with a refs list of blocking references.
  • Only the schema creator, account admin, or team member can delete the schema.
  • Every call is recorded in the account audit log. Don’t put secrets in request fields.
  • High-risk operation. Console JWT callers must pass a second-factor code; app_key callers bypass the MFA prompt but remain audited — treat the key as a secret.

Authorizations

app_key
string
query
required

App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Body

application/json
schema_id
string
required

Mapping schema ID (MongoDB ObjectID hex).

Response

Success

Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.

request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

data
object
required

Empty response body. The server returns data: null on success.