---
title: "Permanently destroy an archived custom type, its table, and its records"
method: DELETE
path: "/v1/object-types/{type}"
tags: ["custom objects"]
---

# Permanently destroy an archived custom type, its table, and its records

`DELETE /v1/object-types/{type}`

## Request

- Base URL: `https://api.indraft.io`
- URL: `https://api.indraft.io/v1/object-types/{type}`
- Auth: HTTP bearer

Drops the table and everything in it. Only an archived type can be destroyed, which is the deliberate pause between deciding and losing, and the ledger rows about a destroyed type are exactly what a drop cannot preserve.

## Path parameters

- `type` string, required

## Response `200`

Success

- object
  - `destroyed` object, required
    - `key` string, required
    - `rows` integer, required
    - `tables` string[], required
  - `requestId` string, required

## Other responses

- `401`: No credential, or one that has been revoked.
- `402`: A product quota is spent, or the subscription is not active.
- `403`: Authenticated, and this capability is not held.
- `404`: No such record, or it belongs to another workspace.
- `409`: A conflict the caller can resolve: a stale expectedVersion, an idempotency key reused for different input, an ambiguous or duplicate identity, or a merge that no longer applies.
- `429`: Infrastructure protection tripped. This is not a product quota.
- `500`: A defect on our side. The hint says so, and carries an incident id.
- `507`: The workspace is at its storage ceiling.

---

[API](https://skmtc.dev/indraft/apis/indraft-api.md) · [All operations](https://skmtc.dev/indraft/apis/indraft-api/llms.txt) · [OpenAPI document](https://skmtc.dev/indraft/apis/indraft-api/revisions/d9bb05346d66?raw)