Permanently delete a custom identifier. This cannot be reversed

Permanently delete a custom identifier. This cannot be reversed. This action uses the same domain service from REST and MCP, so successful calls produce the same canonical domain result.

Authorization and availability

Required scope: custom_identifiers:write. Available in Test and Live. REST operation: DELETE /v1/custom-identifiers/{id}. Equivalent MCP tool: veltor_delete_custom_identifier.

Request schema

Unknown fields are rejected. Path values shown in the route are combined with the JSON body or query input before validation.

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false
}

Example request payload

{
  "id": "00000000-0000-4000-8000-000000000001"
}

Response schema

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "saved": {
      "type": "boolean"
    }
  },
  "required": [
    "saved"
  ],
  "additionalProperties": {}
}

Example success response

REST returns this canonical domain result as JSON. MCP returns the same value in structuredContent and adds only its transport request ID.

{
  "saved": true
}

Errors and recovery

Relevant errors include invalid input (422), missing scope or organization access (403), missing resources (404), revision or idempotency conflicts (409), rate limits (429), and deadline exhaustion (504). Use the returned request ID when investigating a failure.

Idempotency, retries, and timeout

Send a stable idempotency key and reuse it only for an exact retry of this mutation. The server deadline is 5 seconds. Retry only when the error reports retryable true.

Data effect: Review the target and provide explicit confirmation. The action records an audit event and cannot be treated as a read.

cURL

curl -X DELETE https://veltor.dev/v1/custom-identifiers/RESOURCE_ID \
  -H "Authorization: Bearer $VELTOR_SECRET_KEY" \
  -H "Veltor-Organization: $VELTOR_ORGANIZATION" \
  -H "Idempotency-Key: operation_123" \
  -H "Content-Type: application/json" \
  --data '{}'

Node SDK

const result = await veltor.call("/v1/custom-identifiers/RESOURCE_ID", {
  method: "DELETE",
  input: {"id":"00000000-0000-4000-8000-000000000001"},
  idempotencyKey: "operation_123",
});

MCP

veltor_delete_custom_identifier({
  "id": "00000000-0000-4000-8000-000000000001",
  "idempotency_key": "operation_123"
})